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

Update GitHub issue and pull request templates to reflect the current development workflow details #139

Closed
7 of 20 tasks
jprestop opened this issue Sep 14, 2023 · 1 comment
Assignees
Labels
component: repository maintenance Repository maintenance issue priority: medium Medium Priority requestor: METplus Team METplus Development Team type: task An actionable item of work

Comments

@jprestop
Copy link
Contributor

jprestop commented Sep 14, 2023

Describe the Task

Some of the details in the GitHub issue and pull request templates are out of sync with the current development workflow. Update the contents of them to make them accurate.
Use the MET issue as a guide.

Time Estimate

1 hour

Sub-Issues

Consider breaking the task down into sub-issues.
None needed

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2793521

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required

Labels

  • Select component(s)
  • Select priority
  • Select requestor(s)

Projects and Milestone

  • Select Repository and/or Organization level Project(s) or add alert: NEED CYCLE ASSIGNMENT label
  • Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

Task Checklist

See the METplus Workflow for details.

  • Complete the issue definition above, including the Time Estimate and Funding Source.
  • Fork this repository or create a branch of development.
    Branch name: feature_<Issue Number>_<Description>
  • Complete the development and test your changes.
  • Add/update log messages for easier debugging.
  • Add/update unit tests.
  • Add/update documentation.
  • Push local changes to GitHub.
  • Submit a pull request to merge into development.
    Pull request: feature <Issue Number> <Description>
  • Define the pull request metadata, as permissions allow.
    Select: Reviewer(s) and Development issues
    Select: Repository level development cycle Project for the next official release
    Select: Milestone as the next official version
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.
@jprestop jprestop added alert: NEED ACCOUNT KEY Need to assign an account key to this issue priority: medium Medium Priority type: task An actionable item of work requestor: METplus Team METplus Development Team component: repository maintenance Repository maintenance issue labels Sep 14, 2023
@jprestop jprestop added this to the METexpress Future Versions milestone Sep 14, 2023
@jprestop jprestop self-assigned this Sep 14, 2023
@jprestop jprestop removed the alert: NEED ACCOUNT KEY Need to assign an account key to this issue label Sep 14, 2023
@jprestop jprestop linked a pull request Jun 26, 2024 that will close this issue
15 tasks
@jprestop
Copy link
Contributor Author

Closing - this work was completed with PR #157

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: repository maintenance Repository maintenance issue priority: medium Medium Priority requestor: METplus Team METplus Development Team type: task An actionable item of work
Projects
Status: 🏁 Done
Development

Successfully merging a pull request may close this issue.

1 participant