Skip to content
Snippets Groups Projects
  1. Oct 02, 2022
    • Ben Stolman's avatar
      chore(all): add copyright header [AC-3126] · 5c86df49
      Ben Stolman authored and Ethan Reesor's avatar Ethan Reesor committed
      Closes AC-3126. Add Copyright Header.
      
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [ ] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [ ] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [ ] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [ ] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [ ] CI is passing
      - [ ] Merge conflicts are resolved
      - [ ] All discussions are resolved
      
      Related to AC-3126
      5c86df49
  2. May 25, 2022
    • Ethan Reesor's avatar
      test: add test data for merkle hashes [AC-1551] · cdb61db3
      Ethan Reesor authored
      Closes AC-1551. Add a file with hard coded test cases for calculating Merkle hashes so that ecosystem devs can validate their implementations.
      ## Review Checklist
      
      **If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**
      
      - [x] The merge request title is in the format `<change type>(<change scope>): <short description> [<task id>]`
        - For example, `feat(cli): add QR code generation [AC-123]`
        - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
      - [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
      - [x] The change is fully validated by tests that are run during CI
        - In most cases this means a test in "validate.sh"
        - In some cases, a Go test may be acceptable
        - Validation is not applicable to things like documentation updates
        - Purely UI/UX changes can be manually validated, such as changes to human-readable output
        - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
      - [x] The change is marked with one of the validation labels
        - ~"validation::ci/cd" for changes validated by CI tests
        - ~"validation::manual" for changes validated by hand
        - ~"validation::deferred" for changes validated by a follow up merge request
        - ~"validation::not applicable" for changes where validation is not applicable
      
      ## Merge Checklist
      
      - [x] CI is passing
      - [x] Merge conflicts are resolved
      - [x] All discussions are resolved
      
      Related to AC-1551
      cdb61db3
Loading