-
-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TM v4.4.14 (Hotfix) #5093
TM v4.4.14 (Hotfix) #5093
Conversation
Rapid Integration
Suggesting to add two Issue templates that will help user in providing relevant information.
Fix reset-all-bad-imagery API
I added a PR for the BUG template (#5026) and now adding for a FEATURE.
@dakotabenjamin thanks for the comment on the smartphone. I have removed now.
I have now simplified the labels list. As discussed, I have updated the contributing guidelines to reflect the changes and explain the different ways in which people can contribute. The plan is to keep this page up to date with any changes/updates as we continue the collaboration with the collective.
Simplified and updated the text. Removed the page referencing Working Group meetings @dakotabenjamin kept the developer section as is and we can update later on. On the instances, we can also update later on if there are other instances missing.
Updating contributing guidelines
Update issue templates- Feature
Update issue templates
Update READ.ME
Revert "Update READ.ME"
Fix/cfn init codedeploy
Cleans up some code I left in the last release, and rebases to master
Enable OpsGenie webhook by fixing yaml syntax
* Add error message for 403 status code * Update test cases * Update translation source * add sub-codes in error response * add sub-codes on error response for tasks API * fix formatting * fix formatting * fix formatting * add subcodes on projects response * Include error messages for lock error subcodes * add subcode on error response * fix formatting * fix formatting Co-authored-by: Aadesh-Baral <[email protected]>
* Bump marked from 2.1.3 to 4.0.12 in /frontend Bumps [marked](https://github.com/markedjs/marked) from 2.1.3 to 4.0.12. - [Release notes](https://github.com/markedjs/marked/releases) - [Changelog](https://github.com/markedjs/marked/blob/master/.releaserc.json) - [Commits](markedjs/marked@v2.1.3...v4.0.12) --- updated-dependencies: - dependency-name: marked dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> * Use parse to render HTML Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Hel Nershing Thapa <[email protected]>
* Handle self intersection tile exception * Add trim task grid error message Co-authored-by: Hel Nershing Thapa <[email protected]>
* Add error code document in docs
* Fix user tasks sorting * Add option to sort tasks by project id in desc * Add dropdown to sort tasks Co-authored-by: Hel Nershing Thapa <[email protected]>
for task statistics
It would appear that my name was added to the commits from the last release PR and now the branches have diverged. Normally we use the "Rebase and merge" option when merging these released to I want to propose that we actually change our process here and stop merging code back into |
Bumps [sentry-sdk[flask]](https://github.com/getsentry/sentry-python) from 0.19.3 to 1.5.8. - [Release notes](https://github.com/getsentry/sentry-python/releases) - [Changelog](https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md) - [Commits](getsentry/sentry-python@0.19.3...1.5.8) --- updated-dependencies: - dependency-name: sentry-sdk[flask] dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
SonarCloud Quality Gate failed. 0 Bugs No Coverage information |
No description provided.