-
Notifications
You must be signed in to change notification settings - Fork 2
⚠️ CONFLICT! Lineage pull request for: skeleton #22
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
Draft
cisagovbot
wants to merge
570
commits into
develop
Choose a base branch
from
lineage/skeleton
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
772c11f to
adb4ad5
Compare
ffaae3b to
4314400
Compare
992be5d to
0cce140
Compare
This allows all the other good things to happen even if the mypy command fails.
- The setuptools pin was enforcing a version newer than a version from 2016, which seems unnecessary since we are only supporting Python 3.7 and up. - The coveralls pin was enforcing that we not install a particular version from 2020. This again seems unnecessary as we are only supporting Python 3.7 and up.
Python 3.7 is no longer supported: https://www.python.org/downloads/release/python-370/
This is necessary since we have dropped support for Python 3.7. Co-authored-by: David Harris <123905168+dv4harr10@users.noreply.github.com>
Python 3.8 is no longer supported: https://www.python.org/downloads/release/python-380/ Co-authored-by: Nicholas McDonnell <50747025+mcdonnnj@users.noreply.github.com>
This Action will provide information about the usage of GITHUB_TOKEN in the workflow. It should be added to _every_ job in _any_ workflow to provide information for analysis.
This changes the default permissions for the GITHUB_TOKEN used in our GitHub Actions configuration to the minimum required to successfully run.
This is done automatically with the `pre-commit autoupdate` command.
Ensure that all hook ids are sorted alphabetically in each hook entry in our pre-commit configuration.
…bels_workflow Allow the `sync-labels` workflow to be run manually
…ons-monitor Add the `GitHubSecurityLab/actions-permissions/monitor` Action
Explicitly define permissions of `GITHUB_TOKEN` in our GitHub Actions workflows
Update `pre-commit` hook versions
…hooks Add additional hooks from `pre-commit/pre-commit-hooks`
…oks_are_sorted Sort hook ids in each `pre-commit` hook entry
We added a CodeQL configuration in #202 but did not add a badge.
Add a CodeQL badge to the README
The 1.9.0 release of Bandit was flawed due to a failure of the GHA workflows that publish to PyPI and Test PyPI. The 1.9.1 release resolved the issue.
Update `bandit` `pre-commit` hook
Note that using pyproject.toml to configure flake8 requires the addition of the flake8-pyproject Python library.
…e8-config-to-pyproject-toml Revert "Move all Python tool configs to `pyproject.toml`"
…s/download-artifact-6 Bump actions/download-artifact from 5 to 6
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 4 to 5. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](actions/upload-artifact@v4...v5) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
…s/upload-artifact-5 Bump actions/upload-artifact from 4 to 5
This agrees with what is done in the code style badge for the black project. Co-authored-by: Nick <50747025+mcdonnnj@users.noreply.github.com>
Add a code style badge
⚠️ CONFLICT! Lineage pull request for: skeleton
…project-toml-file
Update from `setup.py` to `pyproject.toml`
Python 3.9 reached its EOL on October 31, 2025: https://devguide.python.org/versions/
…pport Remove Python 3.9 support
…/skeleton # Conflicts: # README.md # setup.py
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dependencies
Pull requests that update a dependency file
documentation
This issue or pull request improves or adds to documentation
github-actions
python
shell script
test
upstream update
This issue or pull request pulls in upstream updates
version bump
This issue or pull request increments the version number
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.
Lineage Pull Request: CONFLICT
Lineage has created this pull request to incorporate new changes found in an
upstream repository:
Upstream repository:
https://github.com/cisagov/skeleton-python-library.gitRemote branch:
HEADCheck the changes in this pull request to ensure they won't cause issues with
your project.
The
lineage/skeletonbranch has one or more unresolved merge conflictsthat you must resolve before merging this pull request!
How to resolve the conflicts
Take ownership of this pull request by removing any other assignees.
Clone the repository locally, and reapply the merge:
Review the changes displayed by the
statuscommand. Fix any conflicts andpossibly incorrect auto-merges.
After resolving each of the conflicts,
addyour changes to thebranch,
commit, andpushyour changes:Note that you may append to the default merge commit message
that git creates for you, but please do not delete the existing
content. It provides useful information about the merge that is
being performed.
Wait for all the automated tests to pass.
Check the "Everything is cool" checkbox below:
Mark this draft pull request "Ready for review".
Note: You are seeing this because one of this repository's maintainers has
configured Lineage to open pull requests.
For more information:
🛠 Lineage configurations for this project are stored in
.github/lineage.yml📚 Read more about Lineage