Make GIST_ID as a secret
#112
Merged
Conversation
This file contains 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
|
(Use squash to merge can avoid non-linear commit history) |
|
|
maxam2017
approved these changes
Feb 16, 2024
There was a problem hiding this comment.
I noticed that the active fork also includes the Gist ID in the secret. I believe this is acceptable.
ickynavigator
pushed a commit
to ickynavigator/productive-box
that referenced
this pull request
May 19, 2024
* Update schedule.yml * Update README.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Users can write
GIST_IDin secrets to avoid further modification to files and related commits, which helps for future upstream merges.