feat: expose FUTURE_MONTHS as env var#397
Closed
gczobel wants to merge 1 commit intodaniel-hauser:mainfrom
Closed
Conversation
| DEBUG: "" | ||
| TZ: "Asia/Jerusalem" | ||
| DAYS_BACK: ${{ github.event.inputs.daysBack }} | ||
| FUTURE_MONTHS: ${{ vars.FUTURE_MONTHS }} |
Owner
There was a problem hiding this comment.
What will happen if the variable is not defined for the repo?
Owner
AFAIR cron must be a constant, but i didn't find anything about it in the docs. |
Owner
|
@gczobel Closing as stale, feel free to reopen |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
FUTURE_MONTHS environment variable is not exposed making impossible to modify it without making a local modification of the scrape.yml file.
@daniel-hauser WDYT about add something similar for the cron?