Skip to content

Conversation

cisagovbot
Copy link

@cisagovbot cisagovbot commented Jun 14, 2025

Lineage Pull Request: CONFLICT

Achtung!!!

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 [email protected]:cisagov/action-apb-dashboard.git action-apb-dashboard
    cd action-apb-dashboard
    git remote add skeleton https://github.com/cisagov/skeleton-python-library.git
    git remote set-url --push skeleton no_push
    git switch develop
    git switch --create 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 src/apb_dashboard/_version.py src/example/example.py 
    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. Confirm each item in the "Pre-approval checklist" below.

  7. Remove any of the checklist items that do not apply.

  8. Ensure every remaining checkbox has been checked.

  9. Mark this draft pull request "Ready for review".

✅ Pre-approval checklist

  • ✌️ The conflicts in this pull request have been resolved.
  • All relevant type-of-change labels have been added.
  • All new and existing tests pass.

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

jsf9k and others added 11 commits May 7, 2025 14:10
Version 25.4.0 is the first version to support Fedora 42 in the
Ansible YAML metadata schema.
…sible-lint

Upgrade to the latest version of the `ansible-lint` `pre-commit` hook
Lineage pull request for: skeleton
Update the two testing jobs in the build workflow to test across these
additional platforms (we are currently limited to only free offerings):
- Linux on ARM64
- macOS on ARM64
- Windows on AMD64
Add a short comment that explains why we use the platforms we do in the
`test` and `test-build` jobs in the `build` workflow.

Co-authored-by: Copilot <[email protected]>
Instead of creating a sub-package just to act as a file container we
instead adjust the resource being accessed. This will prevent namespace
cluttering while still providing access to the package data that is
needed. This also follows logically with how the filesystem is
organized where `data/secret.txt` is a resource of the `example`
package.
Breaking the resource path components into separate arguments will
provide a cleaner approach to constructing the resource path.

Co-authored-by: Copilot <[email protected]>
…ackage_data

Adjust how package data is accessed
@cisagovbot cisagovbot added the upstream update This issue or pull request pulls in upstream updates label Jun 14, 2025
@jsf9k jsf9k added the github-actions Pull requests that update GitHub Actions code label Jul 29, 2025
@jsf9k jsf9k force-pushed the lineage/skeleton branch from f7d76b7 to 896a11c Compare July 29, 2025 13:11
@jsf9k jsf9k marked this pull request as ready for review July 29, 2025 13:28
@jsf9k jsf9k enabled auto-merge July 29, 2025 13:28
@jsf9k jsf9k requested a review from a team July 29, 2025 13:28
@jsf9k jsf9k merged commit dd21ed4 into develop Jul 29, 2025
112 checks passed
@jsf9k jsf9k deleted the lineage/skeleton branch July 29, 2025 13:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

github-actions Pull requests that update GitHub Actions code upstream update This issue or pull request pulls in upstream updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants