Bringing changes downstream #45
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
Removed the test configuration part: ``` **Test Configuration**: * Firmware version: * Hardware: * Toolchain: * SDK: ``` this is not relevant to our project and in the instance in which it is, only for mobile which should be supplied under an additional optional info by the developer
…ntegration Downstream changes pr
…end-code Feat/backend/refactor backend code
Note however, the testing issues with need to access env variables has yet to be resolved
Creation of backend related actions for linting, testing and building
Update pull_request_template.md
This update introduces paths to watch for when new changes are introduced for backend
Update bug_report.md
Update CONTRIBUTING.md
Feat/frontend web
Update lint-test-build-golang.yml
…ut the env variables issue
…env-tests Chore: commented out test that uses env variables
…-codecov-upload chore: Update test commands to include code coverage for codecov
Testing occupi-mobile
Update/read me
chore: Update workflow name to include linting and testing for golang
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 11413230 | Triggered | Generic Password | eae2db6 | occupi-backend/tests/utils_test.go | View secret |
| 11413230 | Triggered | Generic Password | ce6441e | occupi-backend/tests/utils_test.go | View secret |
| 11413231 | Triggered | Generic Password | ce6441e | occupi-backend/tests/utils_test.go | View secret |
| 11413231 | Triggered | Generic Password | eae2db6 | occupi-backend/tests/utils_test.go | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
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.
Bringing changes downstream