generated from NASA-PDS/template-repo-java
-
Notifications
You must be signed in to change notification settings - Fork 0
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
As an EN developer, I want to make sure I have access to all PDS repos. #5
Labels
Comments
jordanpadams
changed the title
As an EN developer, I want to make sure I have access to all our PDS EN repos.
As an EN developer, I want to make sure I have access to all PDS repos.
Mar 30, 2021
jordanpadams
added
B12.0
requirement
the current issue is a requirement
p.could-have
skip-i&t
labels
Jul 1, 2021
I've updated the wiki page about new repos to refine the advice on team setup. Doing the READMEs for the |
nutjob4life
added a commit
to NASA-PDS/template-repo-python
that referenced
this issue
Aug 13, 2021
nutjob4life
added a commit
to NASA-PDS/template-repo-java
that referenced
this issue
Aug 13, 2021
MJJoyce
added a commit
to NASA-PDS/template-repo-java
that referenced
this issue
Aug 16, 2021
Partial resolution of NASA-PDS/devops#5 (Java side)
nutjob4life
added a commit
to NASA-PDS/template-repo-python
that referenced
this issue
Aug 17, 2021
Partial resolution for NASA-PDS/devops#5 (Python side)
Finito. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For more information on how to populate this new feature request, see the PDS Wiki on User Story Development:
https://github.com/NASA-PDS/nasa-pds.github.io/wiki/Issue-Tracking#user-story-development
Motivation
...so that I can update / access any of our repositories and source code at any time.
Additional Details
We should make sure all of our repos have the following teams with access:
Additionally, not sure if doing this autonomously is worth the effort at this point. Let's just add this to the template repo READMEs or in a wiki for creating a new repo and call it good.
Acceptance Criteria
Given a member of the @pds-software-committers team has an update to push to a PDS EN repo
When I perform a commit and push to a branch
Then I expect to successfully push to a branch on that repo
Given a member of the @pds-software-pmc or @pdsen-operations team has an update to push to a PDS EN repo
When I perform a commit and push to master on that repo
Then I expect to successfully push to master on that repo
The text was updated successfully, but these errors were encountered: