-
-
Notifications
You must be signed in to change notification settings - Fork 376
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
DevSecOps best practices #7
Comments
Hi @timoa You are most welcome. Please create the PR, I am sure it is going to help everyone. |
I will don't worry 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Amit!
Thanks for this project! It's a perfect start for newcomers on Go backend development!
I'm preparing a Medium post about DevSecOps best practices and I took your project since you released it recently and have enough code to show security use cases.
I was not able to do that with a fork since most of the tools are not supporting it, but I will create PR to help implement automation if you are OK 👍
This is the list of the changes I already made to my cloned project:
These changes are already on the following repo: https://github.com/timoa/secure-go-backend-clean-architecture
I will add the following:
The text was updated successfully, but these errors were encountered: