create issue when polkadot release happens #1045
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
6 tasks
demisx
force-pushed
the
930-automate-new-issue-creation-when-new-polkadot-release-is-published
branch
11 times, most recently
from
1bd3a2c
to
5cd03ef
Compare
demisx
force-pushed
the
930-automate-new-issue-creation-when-new-polkadot-release-is-published
branch
from
5cd03ef
to
4e33974
Compare
demisx
commented
Feb 9, 2023
| @@ -1 +1 @@ | |||
| v0.9.37 | |||
| v0.9.36 | |||
There was a problem hiding this comment.
Setting this to previous full release, so I can test the update on main via cron schedule.
demisx
commented
Feb 9, 2023
| name: Track Polkadot Releases | ||
| on: | ||
| schedule: | ||
| - cron: "*/5 * * * *" |
There was a problem hiding this comment.
Setting cron to every 5 mins for testing on main only. I will change it to once per day afterwords.
demisx
commented
Feb 9, 2023
| - cron: "*/5 * * * *" | ||
| env: | ||
| REPO_URL: https://api.github.com/repos/paritytech/polkadot | ||
| RELEASE_TRACK_FILENAME: .github/workflows/.polkadot-latest-full-release.txt |
There was a problem hiding this comment.
This is the file where we are going to track the latest Polkadot full release.
demisx
commented
Feb 9, 2023
| git config --global user.name 'Frequency CI' | ||
| git config --global user.email '[email protected]' | ||
| git commit -am "Record new Polkadot release version" | ||
| git push origin |
There was a problem hiding this comment.
I chose to commit directly to main instead of creating PR because of:
- This is going to be a very simple one liner commit, i.e. updating
v<old.polkadot.version> -> v<new.polkadot.version> - The commit will be scoped to
.github/workflows/.polkadot-latest-full-release.txtfile only and we don't have to rely on others to remember to merge the PR in timely manner.
|
@saraswatpuneet I am gonna go ahead and merge this one since it's part 1 of #930 and it's kinda holding me back. I can always adjust post-mortem if you find any issues. |
demisx
deleted the
930-automate-new-issue-creation-when-new-polkadot-release-is-published
branch
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.
Goal
The goal of this PR is to record the latest Polkadot release version in frequency repo. It will trigger creating a new GitHub issue later in a different workflow.
Part of #930