Skip to content
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

plugin-material-theme - update path to material-theme #1703

Merged
merged 1 commit into from Oct 8, 2020

Conversation

timbrown5
Copy link
Contributor

Description

I think my original path was wrong (as I am getting 403s when trying to upload - which I am guessing is becase it's uploading to material-theme, when I have permissions to materialtheme). This updates it to the artifactID, not the plugin namespace (which is io/jenkins/plugins/materialtheme).
https://github.com/jenkinsci/material-theme-plugin

Submitter checklist for adding or changing permissions

Always

  • Add link to plugin/component Git repository in description above

Reviewer checklist (not for requesters!)

  • Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
  • Check that the $pluginId Developers team has Admin permissions while granting the access.
  • In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
  • If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

@timbrown5 timbrown5 requested a review from a team as a code owner October 8, 2020 09:32
@timja timja merged commit cff6aea into jenkins-infra:master Oct 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants