-
-
Notifications
You must be signed in to change notification settings - Fork 371
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
Add ability to trigger manual builds #1156
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome work already!
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
e130767
to
65e31d7
Compare
This comment was marked as resolved.
This comment was marked as resolved.
955b7dc
to
0951a22
Compare
added function in go client and cli command, i would need a suggestion about where to place ManualBuildReq, in the meantime i'll refactor and add the names in the ui |
& since it was added to the default event filter, docs have to be adjusted |
@6543 actually it passes a Build to pipeline.Create, so it doesn't fake any existing event, i created the "manual" event The page to be updated is https://woodpecker-ci.org/docs/usage/conditional-execution ? |
Deployment of preview was successful: https://woodpecker-ci-woodpecker-pr-1156.surge.sh |
Co-authored-by: Anbraten <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM if you address the last requested change (https://github.com/woodpecker-ci/woodpecker/pull/1156/files#r966210174)
Where the struct should be duplicated? |
@anbraten @qwerty287 @6543 i've moved the dependency away, but i don't think is the correct place |
I think I'm fine with it, we just never had the case that we need such a struct used to work with http requests... Ci is failing at the docs BTW, can you just run |
Co-authored-by: qwerty287 <[email protected]>
once merged we should create issues that document the followups |
-> #1216 |
are there any other? |
-> #1222 |
closes #83
closes #240
Changelog: