Skip to content

Conversation

@cisagovbot
Copy link

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.git
Remote branch: HEAD

Check the changes in this pull request to ensure they won't cause issues with
your project.

The lineage/skeleton branch has one or more unresolved merge conflicts
that you must resolve before merging this pull request!

How to resolve the conflicts

  1. Take ownership of this pull request by removing any other assignees.

  2. Clone the repository locally, and reapply the merge:

    git clone git@github.com:cisagov/hash-http-content.git hash-http-content
    cd hash-http-content
    git remote add skeleton https://github.com/cisagov/skeleton-python-library.git
    git remote set-url --push skeleton no_push
    git switch develop
    git checkout -b lineage/skeleton --track origin/develop
    git pull skeleton HEAD
    git status
  3. Review the changes displayed by the status command. Fix any conflicts and
    possibly incorrect auto-merges.

  4. After resolving each of the conflicts, add your changes to the
    branch, commit, and push your changes:

    git add README.md 
    git commit
    git push --force --set-upstream origin lineage/skeleton

    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.

  5. Wait for all the automated tests to pass.

  6. Check the "Everything is cool" checkbox below:

    • ✌️ The conflicts in this pull request have been resolved.
  7. 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

@cisagovbot cisagovbot added the upstream update This issue or pull request pulls in upstream updates label Jan 7, 2023
@mcdonnnj mcdonnnj force-pushed the lineage/skeleton branch from ffaae3b to 4314400 Compare May 25, 2024 01:06
@dav3r dav3r mentioned this pull request Jun 3, 2024
7 tasks
mcdonnnj and others added 18 commits October 2, 2024 00:27
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.
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
…hooks

Add additional hooks from `pre-commit/pre-commit-hooks`
…oks_are_sorted

Sort hook ids in each `pre-commit` hook entry
mcdonnnj and others added 29 commits November 17, 2025 11:05
We added a CodeQL configuration in #202 but did not add a badge.
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.
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>
⚠️ CONFLICT! Lineage pull request for: skeleton
Python 3.9 reached its EOL on October 31, 2025:
https://devguide.python.org/versions/
…/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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants