Merge dev changes to test #136
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
…ckend (#130) Bumps [dotnet-reportgenerator-globaltool](https://github.com/danielpalme/ReportGenerator) from 5.3.6 to 5.3.7. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/danielpalme/ReportGenerator/releases">dotnet-reportgenerator-globaltool's releases</a>.</em></p> <blockquote> <h2>ReportGenerator_5.3.7</h2> <h1>Changes:</h1> <ul> <li>Exclude empty modules/assemblies from reports -Fix sort direction triangles (contributed by <a href="https://github.com/YuriyDurov"><code>@YuriyDurov</code></a>) -<a href="https://redirect.github.com/danielpalme/ReportGenerator/issues/602">#602</a>: HtmlSummary and Html_BlueRed_Summary report types now also create an index.html file</li> </ul> <p>This release requires .NET Framework 4.7 or .NET 6.0/7.0/8.0</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/danielpalme/ReportGenerator/commit/0fa15f62323bfc40012bf4b4ec408164c05709ae"><code>0fa15f6</code></a> Release 5.3.7</li> <li><a href="https://github.com/danielpalme/ReportGenerator/commit/6c6900016cef262119c40255fbd5863d5476e60f"><code>6c69000</code></a> <a href="https://redirect.github.com/danielpalme/ReportGenerator/issues/602">#602</a>: HtmlSummary and Html_BlueRed_Summary report types now also create an in...</li> <li><a href="https://github.com/danielpalme/ReportGenerator/commit/2ddf1ee06eaf5431471a5d3f23e2f5fcc87b7f03"><code>2ddf1ee</code></a> Update default metric thresholds</li> <li><a href="https://github.com/danielpalme/ReportGenerator/commit/9913e986afb40dd16b1ec2b233e1b624396cb460"><code>9913e98</code></a> Update Angular</li> <li><a href="https://github.com/danielpalme/ReportGenerator/commit/673e3b910ede189a8004805999636e0e1300da35"><code>673e3b9</code></a> Merge branch 'main' of <a href="https://github.com/YuriyDurov/ReportGenerator">https://github.com/YuriyDurov/ReportGenerator</a></li> <li><a href="https://github.com/danielpalme/ReportGenerator/commit/2c24ebec838b0da37e78f3a2a2d941a631c948a9"><code>2c24ebe</code></a> Fix default sort icon values</li> <li><a href="https://github.com/danielpalme/ReportGenerator/commit/c0e33f7e7e1ccda2ec9285b32f1f60d691e02a4c"><code>c0e33f7</code></a> Fix coverage info ordering</li> <li><a href="https://github.com/danielpalme/ReportGenerator/commit/2ce9d61185de1330281ac700aafa0f0f781a66e2"><code>2ce9d61</code></a> Fix risk hotspots ordering</li> <li><a href="https://github.com/danielpalme/ReportGenerator/commit/6c8a5e847aadfddb9cea454c46a9c55b2a4f96b7"><code>6c8a5e8</code></a> Exclude empty modules/assemblies from reports</li> <li>See full diff in <a href="https://github.com/danielpalme/ReportGenerator/compare/v5.3.6...v5.3.7">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…1 to 1.21.0 in /src/backend in the microsoft group (#129) Bumps the microsoft group in /src/backend with 1 update: Microsoft.VisualStudio.Azure.Containers.Tools.Targets. Updates `Microsoft.VisualStudio.Azure.Containers.Tools.Targets` from 1.20.1 to 1.21.0 [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> --------- Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: dependabot[bot] <dependabot[bot]@users.noreply.github.com>
github-actions
bot
added
the
dependencies
<!--- Provide a general summary of your changes in the Title above --> ## Description 💬 <!--- Describe your changes in detail --> ## Motivation and Context 🥅 <!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here. --> ## How has this been tested? 🧪 <!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, tests ran to see how --> <!--- your change affects other areas of the code, etc. --> - [ ] Local build ⚒️ - [ ] Local tests 🧪 - [ ] (optional) Local run and endpoint tested in swagger 🚀 ## Screenshots (if appropriate) 💻 ## Types of changes 🌊 <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) ## Checklist ☑️ <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] The pull request title starts with the jira case number (when applicable), e.g. "TEST-1234 Add some feature" - [ ] The person responsible for following up on requested review changes has been assigned to the pull request - [ ] My code follows the code style of this project. - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. ## Highly optional checks, only use these if you have a reason to do so ✔️ - [ ] This PR changes the database so I have added the *create-diagram* label to assist reviewers with a db diagram - [ ] This PR changes platform or backend and I need others to be able to test against these changes before merging to dev, so I have added the *deploy-azure* label to deploy before merging the PR ## Checklist for the approver ✅ - [ ] I've checked the files view for spelling issues, code quality warnings and similar - [ ] I've waited until all checks have passed (green check/without error) - [ ] I've checked that only the intended files are changed
<!--- Provide a general summary of your changes in the Title above --> ## Description 💬 <!--- Describe your changes in detail --> ## Motivation and Context 🥅 <!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here. --> ## How has this been tested? 🧪 <!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, tests ran to see how --> <!--- your change affects other areas of the code, etc. --> - [ ] Local build ⚒️ - [ ] Local tests 🧪 - [ ] (optional) Local run and endpoint tested in swagger 🚀 ## Screenshots (if appropriate) 💻 ## Types of changes 🌊 <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) ## Checklist ☑️ <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] The pull request title starts with the jira case number (when applicable), e.g. "TEST-1234 Add some feature" - [ ] The person responsible for following up on requested review changes has been assigned to the pull request - [ ] My code follows the code style of this project. - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. ## Highly optional checks, only use these if you have a reason to do so ✔️ - [ ] This PR changes the database so I have added the *create-diagram* label to assist reviewers with a db diagram - [ ] This PR changes platform or backend and I need others to be able to test against these changes before merging to dev, so I have added the *deploy-azure* label to deploy before merging the PR ## Checklist for the approver ✅ - [ ] I've checked the files view for spelling issues, code quality warnings and similar - [ ] I've waited until all checks have passed (green check/without error) - [ ] I've checked that only the intended files are changed
test-e2e✅ Build successful✅ No linting issues 🎊 |
Todo Commenter.github/actions/frontend-build/action.ymlTODO:
FIXME:
BUG:
.github/workflows/deploy-cd.ymlTODO:
@hwinther Please take a look 👀 |
✅ Build successful |
frontend✅ Build successful✅ No linting issues 🎊 |
SummarySummary
CoverageWebApi - 8.7%
|
|
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.
Automatically created pull-request in order to merge changes that were recently pushed to the dev branch, back to test