Record merged PRs in the new repository #225
Open
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
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.
This change makes it so that, whenever a pull request is merged on this repository, an issue in the new repository will be automatically updated to record that.
This will make it easier to keep track of changes in the SAS code while the Python model is being developed.
More technical notes: In order for this to run, it needs a personal access token with enough permissions to modify the issue comments in hivpy. The token should be stored as a secret in this repository (I have used the name
PAT_FOR_ISSUEhere). I have created one such token under my account and stored it in this repository, but it will expire on December 31, and my access may lapse before then anyway! Therefore, someone else will need to create a new one, and update the value of the secret.