Test Release #9
Merged
Test Release #9
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
#8) * Add a markdown file for dashboard descriptions, link new file in README.md (cisagov#138) * Add a markdown file for dashboard descriptions ## 🗣 Description ## <!-- Describe the "what" of your changes in detail. --> Add dashboard-descriptions.md in /docs/markdown/reference. Add a link to this file within the main README.md's table of contents. ### 💭 Motivation and context <!-- Why is this change required? --> <!-- What problem does this change solve? How did you solve it? --> <!-- Mention any related issue(s) here using appropriate keywords such --> <!-- as "closes" or "resolves" to auto-close them on merge. --> The LME repository does not have a location for dashboard descriptions. ## 🧪 Testing <!-- How did you test your changes? How could someone else test this PR? --> <!-- Include details of your testing environment, and the tests you ran to --> <!-- see how your change affects other areas of the code, etc. --> N/A ## ✅ Pre-approval checklist ## - [x] Changes are limited to a single goal **AND** the title reflects this in a clear human readable format - [x] I have read and agree to LME's [CONTRIBUTING.md](https://github.com/cisagov/LME/CONTRIBUTING.md) document. - [x] The PR adheres to LME's requirements in [RELEASES.md](https://github.com/cisagov/LME/RELEASES.md#steps-to-submit-a-PR) - [x] These code changes follow [cisagov code standards](https://github.com/cisagov/development-guide). - [x] All relevant repo and/or project documentation has been updated to reflect the changes in this PR. ## ✅ Post-merge Checklist - [x] Squash all commits into one PR level commit - [x] Delete the branch to keep down number of branches * Update README.md to include dashboard-descriptions.md * Update wording for computer software overview dashboard * Fix some grammatical changes in dashboard-descriptions.md * Release 1.3.1 merge into main (cisagov#154) * Update retention function to fix retention policy bug (cisagov#143) * Updated troubleshooting guide to account for index management (cisagov#134) * Update upgrading.md to account for 1.3.1 (cisagov#151) * Update upgrading.md * Update upgrading.md --------- Co-authored-by: Andrew Arz <[email protected]> * Fixes dashboard update not importing on fresh install (cisagov#167) (cisagov#169) * Fixes dashboard update not importing on fresh install cisagov#165 * Update upgrading.md to include status on v1.3.2, along with revisions to the document overall * remove step 4 from upgrading.md; add additional instructions for v1.3.2 --------- Co-authored-by: Clint Baxley <[email protected]> Co-authored-by: Clint Baxley <[email protected]> * create run_release.yaml github action workflow * create test commits for sample PR * test custom date and body * making a test commit 1 --------- Co-authored-by: Andrew Arz <[email protected]> Co-authored-by: Clint Baxley <[email protected]> Co-authored-by: Clint Baxley <[email protected]>
#10) * Add a markdown file for dashboard descriptions, link new file in README.md (cisagov#138) * Add a markdown file for dashboard descriptions ## 🗣 Description ## <!-- Describe the "what" of your changes in detail. --> Add dashboard-descriptions.md in /docs/markdown/reference. Add a link to this file within the main README.md's table of contents. ### 💭 Motivation and context <!-- Why is this change required? --> <!-- What problem does this change solve? How did you solve it? --> <!-- Mention any related issue(s) here using appropriate keywords such --> <!-- as "closes" or "resolves" to auto-close them on merge. --> The LME repository does not have a location for dashboard descriptions. ## 🧪 Testing <!-- How did you test your changes? How could someone else test this PR? --> <!-- Include details of your testing environment, and the tests you ran to --> <!-- see how your change affects other areas of the code, etc. --> N/A ## ✅ Pre-approval checklist ## - [x] Changes are limited to a single goal **AND** the title reflects this in a clear human readable format - [x] I have read and agree to LME's [CONTRIBUTING.md](https://github.com/cisagov/LME/CONTRIBUTING.md) document. - [x] The PR adheres to LME's requirements in [RELEASES.md](https://github.com/cisagov/LME/RELEASES.md#steps-to-submit-a-PR) - [x] These code changes follow [cisagov code standards](https://github.com/cisagov/development-guide). - [x] All relevant repo and/or project documentation has been updated to reflect the changes in this PR. ## ✅ Post-merge Checklist - [x] Squash all commits into one PR level commit - [x] Delete the branch to keep down number of branches * Update README.md to include dashboard-descriptions.md * Update wording for computer software overview dashboard * Fix some grammatical changes in dashboard-descriptions.md * Release 1.3.1 merge into main (cisagov#154) * Update retention function to fix retention policy bug (cisagov#143) * Updated troubleshooting guide to account for index management (cisagov#134) * Update upgrading.md to account for 1.3.1 (cisagov#151) * Update upgrading.md * Update upgrading.md --------- Co-authored-by: Andrew Arz <[email protected]> * Fixes dashboard update not importing on fresh install (cisagov#167) (cisagov#169) * Fixes dashboard update not importing on fresh install cisagov#165 * Update upgrading.md to include status on v1.3.2, along with revisions to the document overall * remove step 4 from upgrading.md; add additional instructions for v1.3.2 --------- Co-authored-by: Clint Baxley <[email protected]> Co-authored-by: Clint Baxley <[email protected]> * create run_release.yaml github action workflow * create test commits for sample PR * test custom date and body * making a test commit 1 * test commit --------- Co-authored-by: Andrew Arz <[email protected]> Co-authored-by: Clint Baxley <[email protected]> Co-authored-by: Clint Baxley <[email protected]>
#11) * Add a markdown file for dashboard descriptions, link new file in README.md (cisagov#138) * Add a markdown file for dashboard descriptions ## 🗣 Description ## <!-- Describe the "what" of your changes in detail. --> Add dashboard-descriptions.md in /docs/markdown/reference. Add a link to this file within the main README.md's table of contents. ### 💭 Motivation and context <!-- Why is this change required? --> <!-- What problem does this change solve? How did you solve it? --> <!-- Mention any related issue(s) here using appropriate keywords such --> <!-- as "closes" or "resolves" to auto-close them on merge. --> The LME repository does not have a location for dashboard descriptions. ## 🧪 Testing <!-- How did you test your changes? How could someone else test this PR? --> <!-- Include details of your testing environment, and the tests you ran to --> <!-- see how your change affects other areas of the code, etc. --> N/A ## ✅ Pre-approval checklist ## - [x] Changes are limited to a single goal **AND** the title reflects this in a clear human readable format - [x] I have read and agree to LME's [CONTRIBUTING.md](https://github.com/cisagov/LME/CONTRIBUTING.md) document. - [x] The PR adheres to LME's requirements in [RELEASES.md](https://github.com/cisagov/LME/RELEASES.md#steps-to-submit-a-PR) - [x] These code changes follow [cisagov code standards](https://github.com/cisagov/development-guide). - [x] All relevant repo and/or project documentation has been updated to reflect the changes in this PR. ## ✅ Post-merge Checklist - [x] Squash all commits into one PR level commit - [x] Delete the branch to keep down number of branches * Update README.md to include dashboard-descriptions.md * Update wording for computer software overview dashboard * Fix some grammatical changes in dashboard-descriptions.md * Release 1.3.1 merge into main (cisagov#154) * Update retention function to fix retention policy bug (cisagov#143) * Updated troubleshooting guide to account for index management (cisagov#134) * Update upgrading.md to account for 1.3.1 (cisagov#151) * Update upgrading.md * Update upgrading.md --------- Co-authored-by: Andrew Arz <[email protected]> * Fixes dashboard update not importing on fresh install (cisagov#167) (cisagov#169) * Fixes dashboard update not importing on fresh install cisagov#165 * Update upgrading.md to include status on v1.3.2, along with revisions to the document overall * remove step 4 from upgrading.md; add additional instructions for v1.3.2 --------- Co-authored-by: Clint Baxley <[email protected]> Co-authored-by: Clint Baxley <[email protected]> * create run_release.yaml github action workflow * create test commits for sample PR * test custom date and body * making a test commit 1 * test commit * test commit --------- Co-authored-by: Andrew Arz <[email protected]> Co-authored-by: Clint Baxley <[email protected]> Co-authored-by: Clint Baxley <[email protected]>
#12) * Add a markdown file for dashboard descriptions, link new file in README.md (cisagov#138) * Add a markdown file for dashboard descriptions ## 🗣 Description ## <!-- Describe the "what" of your changes in detail. --> Add dashboard-descriptions.md in /docs/markdown/reference. Add a link to this file within the main README.md's table of contents. ### 💭 Motivation and context <!-- Why is this change required? --> <!-- What problem does this change solve? How did you solve it? --> <!-- Mention any related issue(s) here using appropriate keywords such --> <!-- as "closes" or "resolves" to auto-close them on merge. --> The LME repository does not have a location for dashboard descriptions. ## 🧪 Testing <!-- How did you test your changes? How could someone else test this PR? --> <!-- Include details of your testing environment, and the tests you ran to --> <!-- see how your change affects other areas of the code, etc. --> N/A ## ✅ Pre-approval checklist ## - [x] Changes are limited to a single goal **AND** the title reflects this in a clear human readable format - [x] I have read and agree to LME's [CONTRIBUTING.md](https://github.com/cisagov/LME/CONTRIBUTING.md) document. - [x] The PR adheres to LME's requirements in [RELEASES.md](https://github.com/cisagov/LME/RELEASES.md#steps-to-submit-a-PR) - [x] These code changes follow [cisagov code standards](https://github.com/cisagov/development-guide). - [x] All relevant repo and/or project documentation has been updated to reflect the changes in this PR. ## ✅ Post-merge Checklist - [x] Squash all commits into one PR level commit - [x] Delete the branch to keep down number of branches * Update README.md to include dashboard-descriptions.md * Update wording for computer software overview dashboard * Fix some grammatical changes in dashboard-descriptions.md * Release 1.3.1 merge into main (cisagov#154) * Update retention function to fix retention policy bug (cisagov#143) * Updated troubleshooting guide to account for index management (cisagov#134) * Update upgrading.md to account for 1.3.1 (cisagov#151) * Update upgrading.md * Update upgrading.md --------- Co-authored-by: Andrew Arz <[email protected]> * Fixes dashboard update not importing on fresh install (cisagov#167) (cisagov#169) * Fixes dashboard update not importing on fresh install cisagov#165 * Update upgrading.md to include status on v1.3.2, along with revisions to the document overall * remove step 4 from upgrading.md; add additional instructions for v1.3.2 --------- Co-authored-by: Clint Baxley <[email protected]> Co-authored-by: Clint Baxley <[email protected]> * create run_release.yaml github action workflow * create test commits for sample PR * test custom date and body * making a test commit 1 * test commit * test commit --------- Co-authored-by: Andrew Arz <[email protected]> Co-authored-by: Clint Baxley <[email protected]> Co-authored-by: Clint Baxley <[email protected]>
Merged
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.
see if we get these four PRs added correctly into main branch version history so release notes are generated correctly