Build: [AEA-3605] - Clean up PR workflows #25
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…github.com:NHSDigital/nhs-fhir-middy-error-handler into aea-3605-move-middy-error-handler-to-seperate-repo
…rror-handler-to-seperate-repo
|
This branch is work on a ticket in the NHS Digital APM JIRA Project. Here's a handy link to the ticket: AEA-3605 |
|
JackSpagnoliNHS
deleted the
aea-3605-move-middy-error-handler-to-seperate-repo
branch
originalphil
pushed a commit
that referenced
this pull request
Jan 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Remove items from this list if they are not relevant. Remove this line once this has been done
Details
Add any summary information of what is in the change. Remove this line if you have nothing to add.
Pull Request Naming
Pull requests should be named using the following format:
Tag can be one of:
Fix- for a bug fix. (Patch release)Update- either for a backwards-compatible enhancement or for a rule change that adds reported problems. (Patch release)New- implemented a new feature. (Minor release)Breaking- for a backwards-incompatible enhancement or feature. (Major release)Docs- changes to documentation only. (Patch release)Build- changes to build process only. (No release)Upgrade- for a dependency upgrade. (Patch release)Chore- for refactoring, adding tests, etc. (anything that isn't user-facing). (Patch release)Correct tagging is necessary for our automated versioning and release process (Release).
The description of your pull request will be used as the commit message for the merge, and also be included in the changelog. Please ensure that your title is sufficiently descriptive.