Nothing Special   »   [go: up one dir, main page]

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Update apify_platform.mdx #2630

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs: Update apify_platform.mdx #2630

wants to merge 1 commit into from

Conversation

Pokrt
Copy link
@Pokrt Pokrt commented Aug 23, 2024

I had problem where to set my own env variables so I added useful link into the documentation.

I had problem where to set my own env variables so I added useful link into the documentation.
@Pokrt Pokrt changed the title Update apify_platform.mdx docs: Update apify_platform.mdx Aug 23, 2024
@B4nan
Copy link
Member
B4nan commented Aug 28, 2024

i am not completely opposed by adding the link there, but it feels like you missed the fact that you don't need any tooling to set env var. also you updated only one version snapshot, your change would be forgotten on next feature release.

@fnesveda fnesveda added the t-tooling Issues with this label are in the ownership of the tooling team. label Sep 4, 2024
@Pokrt
Copy link
Author
Pokrt commented Sep 6, 2024

I know that I can set env vars on the apify platform, what branch should i put it into to be included in next release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t-tooling Issues with this label are in the ownership of the tooling team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants