Skip to content

Conversation

@cisagovbot
Copy link

@cisagovbot cisagovbot commented Jul 15, 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-ansible-role.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/ansible-role-cyhy-logrotate.git ansible-role-cyhy-logrotate
    cd ansible-role-cyhy-logrotate
    git remote add skeleton https://github.com/cisagov/skeleton-ansible-role.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 molecule/default/requirements.yml 
    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 3 commits July 15, 2025 13:26
Debian Buster is no longer supported by the standard Debian package
repository URLs because it is so outdated; therefore, this platform
must be switched to use the Debian Archive package package
repositories.

Note that the cisagov/ansible-role-debian-archive role must be
applied *before* cisagof/ansible-role-upgrade, so the role *must* be
added to the upgrade.yml playbook.
…for-buster

Use Debian Archive package repositories for Debian Buster
@cisagovbot cisagovbot added the upstream update This issue or pull request pulls in upstream updates label Jul 15, 2025
@jsf9k jsf9k force-pushed the lineage/skeleton branch from fe89cee to ca6d20b Compare July 18, 2025 18:59
@jsf9k jsf9k unassigned dav3r and mcdonnnj Jul 18, 2025
@jsf9k jsf9k added the dependencies Pull requests that update a dependency file label Jul 18, 2025
@jsf9k jsf9k marked this pull request as ready for review July 18, 2025 19:45
@jsf9k jsf9k requested review from dav3r, jsf9k and mcdonnnj as code owners July 18, 2025 19:45
@jsf9k jsf9k enabled auto-merge July 18, 2025 19:45
@jsf9k jsf9k requested a review from a team July 18, 2025 19:46
@jsf9k jsf9k merged commit c1c5aa8 into develop Jul 21, 2025
53 checks passed
@jsf9k jsf9k deleted the lineage/skeleton branch July 21, 2025 15:36
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 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