Skip to content

Implement read-only-api as a new sub API - #628

Draft
patrick-austin wants to merge 3 commits into
developfrom
patrick/read_only_api
Draft

Implement read-only-api as a new sub API#628
patrick-austin wants to merge 3 commits into
developfrom
patrick/read_only_api

Conversation

@patrick-austin

Copy link
Copy Markdown
Contributor

This PR will close #{issue number}

Description

Enter a description of the changes here

Testing Instructions

Add a set up instructions describing how the reviewer should test the code

  • Review code
  • Check GitHub Actions build
  • If icatdb Generator Script Consistency Test CI job fails, is this because of a deliberate change made to the script to change generated data (which isn't actually a problem) or is here an underlying issue with the changes made?
  • Review changes to test coverage
  • Does this change mean a new patch, minor or major version should be made? If so, does one of the commit messages feature fix:, feat: or BREAKING CHANGE: so a release is automatically made via GitHub Actions upon merge?
  • {more steps here}

Agile Board Tracking

Connect to #{issue number}

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.

1 participant