-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add upload permissions for configuration-as-code-test-harness #1359
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
Conversation
jetersen
left a comment
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
|
Build failed; the context from the latest run is: Expand to view |
Co-Authored-By: Joseph Petersen <[email protected]>
|
|
Needs auth from @ewelinawilkosz for the change to the component yaml. |
It was authorised here: One was missed |
Description
Add permissions for new test-harness for configuration-as-code-plugin: jenkinsci/configuration-as-code-plugin#1215
And update @Casz to be security contact for snakeyaml component (he's the contact for all other configuration-as-code component's, this one was missed in the update.
Submitter checklist for changing permissions
Always
For a new permissions file only
permissions/directoryartifactId(pom.xml) is used forname(permissions YAML file).groupId/artifactId(pom.xml) are correctly represented inpath(permissions YAML file)