Introduces token operations on project #15261
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
github-actions
bot
added
Documentation 📖
hennevogel
force-pushed
the
feature/token_operations_on_project
branch
3 times, most recently
from
d7d07e1
to
47d61cc
Compare
hennevogel
force-pushed
the
feature/token_operations_on_project
branch
from
47d61cc
to
45d4647
Compare
hennevogel
force-pushed
the
feature/token_operations_on_project
branch
2 times, most recently
from
c47270a
to
f2a4684
Compare
|
Review app will appear here: http://obs-reviewlab.opensuse.org/hennevogel-featuretoken_operations_on_project |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #15261 +/- ##
=======================================
Coverage 86.24% 86.25%
=======================================
Files 786 786
Lines 25744 25766 +22
=======================================
+ Hits 22204 22224 +20
- Misses 3540 3542 +2 |
hennevogel
force-pushed
the
feature/token_operations_on_project
branch
2 times, most recently
from
dd4b6bc
to
4348319
Compare
hennevogel
force-pushed
the
feature/token_operations_on_project
branch
from
4348319
to
c762f1d
Compare
There are two types of trigger routes: On /trigger you can trigger an type of `Token` On /trigger/[rebuild, release, runservice, workflow] you can trigger only this type of `Token` If a `Token` has a `Package` the operation is executed on this `Package`. If a `Token` does not have a `Package` you can set one via the project/package parameters and the operation is executed on this `Package`. If a `Token::Rebuild` or a `Token::Release` has no `Package` you can set a `Project` via the project parameter and the operation is executed on this `Project`. Co-authored-by: Adrian Schröter <[email protected]> Co-authored-by: Eduardo Navarro <[email protected]>
Drop the minitest test Co-authored-by: Eduardo Navarro <[email protected]>
Co-authored-by: Eduardo Navarro <[email protected]>
hennevogel
force-pushed
the
feature/token_operations_on_project
branch
from
c762f1d
to
8b874ef
Compare
eduardoj
approved these changes
Dec 20, 2023
This was referenced Dec 21, 2023
Merged
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.
There are two types of trigger routes:
On /trigger you can trigger an type of
TokenexceptToken::WorkflowOn /trigger/[rebuild, release, runservice, workflow] you can trigger only this type of
TokenIf a
Tokenhas aPackagethe operation is executed on thisPackage.If a
Tokendoes not have aPackageyou can set one via the project/packageparameters and the operation is executed on this
Package.If a
Token::Rebuildor aToken::Releasehas noPackageyou can set aProjectvia the project parameter and the operation is executed on thisProject.API Docu: https://obs-reviewlab.opensuse.org/hennevogel-featuretoken_operations_on_project/apidocs/index.html#/Trigger/post_trigger