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

Create checksum for released code #209

Closed
20 tasks
bikegeek opened this issue Aug 31, 2022 · 0 comments · Fixed by #211
Closed
20 tasks

Create checksum for released code #209

bikegeek opened this issue Aug 31, 2022 · 0 comments · Fixed by #211
Assignees
Labels
type: task An actionable item of work
Milestone

Comments

@bikegeek
Copy link
Collaborator

(dtcenter/METplus#1769)

Describe the Task

Add task in GHA to create a SHA checksum

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

Sub-Issues

Consider breaking the task down into sub-issues.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

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 PROJECT 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 develop.
    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 develop.
    Pull request: feature <Issue Number> <Description>
  • Define the pull request metadata, as permissions allow.
    Select: Reviewer(s) and Linked 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.
@bikegeek bikegeek added type: task An actionable item of work alert: NEED ACCOUNT KEY Need to assign an account key to this issue labels Aug 31, 2022
@bikegeek bikegeek added this to the METcalcpy-2.0 milestone Aug 31, 2022
@bikegeek bikegeek self-assigned this Aug 31, 2022
@hankenstein2 hankenstein2 moved this from To Do to In Progress in METplus-Analysis-5.0-beta3 (09/14/22) Sep 7, 2022
@bikegeek bikegeek moved this from In Progress to Pull Request Review in METplus-Analysis-5.0-beta3 (09/14/22) Sep 8, 2022
@bikegeek bikegeek linked a pull request Sep 8, 2022 that will close this issue
13 tasks
@bikegeek bikegeek moved this to Pull Request Review in METplus-Analysis-5.0-beta3 (09/14/22) Sep 8, 2022
@bikegeek bikegeek moved this from Pull Request Review to Done in METplus-Analysis-5.0-beta3 (09/14/22) Sep 14, 2022
@bikegeek bikegeek closed this as completed Mar 1, 2023
@jprestop jprestop removed the alert: NEED ACCOUNT KEY Need to assign an account key to this issue label Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task An actionable item of work
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants