-
Notifications
You must be signed in to change notification settings - Fork 20
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
ci: trigger release workflow after creating dev tag #1610
Conversation
This repo has @d2iq-mergebot integration. You can perform the following commands by submitting a comment. Submit a comment with content "@d2iq-mergebot help" to view more detailed help text and examples. Be sure the have a look at the mergebot documentation, too.For help using mergebot, please refer to the README file here: https://github.com/mesosphere/mergebot/blob/main/README.md |
Pull Request Test Coverage Report for Build 6262753345
💛 - Coveralls |
23dec44
to
b1cea04
Compare
b1cea04
to
ebd0184
Compare
c7af536
to
1167b59
Compare
855bd3b
to
ea0fd6d
Compare
ea0fd6d
to
5d3f743
Compare
5d3f743
to
6ecae0c
Compare
6ecae0c
to
790ed92
Compare
I think you can get rid of most of the existing git config stuff in there btw |
I tried getting rid of the git user config and it complained: https://github.com/mesosphere/kommander-applications/actions/runs/6253295944/job/16978375666 i was able to get rid of the private repo config step though |
ae86c6a
to
100d27c
Compare
What problem does this PR solve?:
Releases aren't being triggered when we create tags. this option allows us to use the built in github token and just use a workflow dispatch to do the release. alternatively, using a PAT should also work.
Which issue(s) does this PR fix?:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Checklist