Update plugin-vstestrunner.yml #1025
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
batmat
approved these changes
Feb 7, 2019
|
We got a green build 💚 |
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.
Description
New maintainer for vstestrunner-plugin
https://groups.google.com/forum/#!topic/jenkinsci-dev/-XfjxgJlSFM
https://github.com/jenkinsci/vstestrunner-plugin/
hi their @Casz
Submitter checklist for changing permissions
Always
For a newly hosted plugin only
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)plugin-${artifactId}.ymlfor pluginsWhen adding new uploaders (this includes newly created permissions files)
@mention an existing maintainer to confirm the permissions request, if applicable