-
Notifications
You must be signed in to change notification settings - Fork 5
release(1.2.0): Release version 1.2.0 #103
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
Merged
Merged
Conversation
This file contains hidden or 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
… actions start pointing at develop as our default branch to match reality
SAST is already running via the settings on this repo
also turn off our testing branch push runs
works in conjunction with the if on the last step to run always, excpet only publish the docs on the main branch
we can always skip using a flag in our commit messages if needed https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/skipping-workflow-runs
feat(CI): Move CI to Github Actions
… we use it in also appeases flake8
…on in our local settings instead of inheriting them
…le-prod with local auth use case
…emp-fix ci(docs): only build docs on main
Move flake8 + black to Ruff
Fixes pytest warning: `No directory at: /home/runner/work/SCRAM/SCRAM/staticfiles/` --------- Co-authored-by: Chris Cummings <chriscummings@es.net>
A couple extra things: * Add a Behave test with Python 3.13, similar to the pytest one * Make the Python version an argument to the Dockerfiles
This lets you run prod with a local postgres instance. We prolly need to document the vault stuff, but I think that's better suited for #88 to handle. I *think* this MR is ready to rock, it's deployed and working on `scram-pentest.ocean.cu-es.net` presently.
|
Minimum allowed coverage is Generated by 🐒 cobertura-action against 6810e74 |
release(1.1.1)
samoehlert
approved these changes
Dec 23, 2024
Collaborator
samoehlert
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to get this released
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.
No description provided.