Skip to content

Conversation

cisagovbot
Copy link

@cisagovbot cisagovbot commented Sep 24, 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 [email protected]:cisagov/ansible-role-okta-asa-server-agent.git ansible-role-okta-asa-server-agent
    cd ansible-role-okta-asa-server-agent
    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 .config/molecule/config.yml .github/workflows/build.yml meta/main.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

mcdonnnj and others added 30 commits May 28, 2025 11:15
This adds a `ci` block to the pre-commit configurations to control the
behavior of the pre-commit.ci GitHub app.
We currently use the `develop` branch as our reference for the
cisagov/setup-env-github-action action in the build workflow. We will
instead use the major version tag which puts our usage of this action
in line with how we use other actions in our workflows.
He has one now that Trixie has been officially released.
Now that Forky is tested we may as well test it.
The script was not updated when we switched to using a default
configuration file for most of the Molecule configuration.
Update the helper script to update Docker images used in the Molecule
testing configuration to store the default file in a variable. This
will DRY out the code a bit to ensure the usage information matches the
behavior of the script without changing values in multiple locations.
This includes updating the dependabot configuration, adding a new
`label-prs.yml` GitHub Actions workflow, and adding a suitable
configuration file for the actions/labeler action used by the
aforementioned workflow.
Bumps [actions/labeler](https://github.com/actions/labeler) from 5 to 6.
- [Release notes](https://github.com/actions/labeler/releases)
- [Commits](actions/[email protected])

---
updated-dependencies:
- dependency-name: actions/labeler
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 5 to 6.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@v5...v6)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [actions/setup-go](https://github.com/actions/setup-go) from 5 to 6.
- [Release notes](https://github.com/actions/setup-go/releases)
- [Commits](actions/setup-go@v5...v6)

---
updated-dependencies:
- dependency-name: actions/setup-go
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Instead of using the default labels for the `github-actions` package
ecosystem we specify the labels explicitly. This is done to ensure that
dependabot uses our `github-actions` label instead of the default of
`github_actions`. We must also explicitly specify the `dependencies`
label since we are overriding the default label values.
Change the check from looking for specific text in the version output
to using the `--test` option. This will provide a more robust
implementation of this check that does not have to worry about output
format stability.

Co-authored-by: Copilot <[email protected]>
Use a version tag for `cisagov/setup-env-github-action`
…s/setup-python-6

Bump actions/setup-python from 5 to 6
…s/setup-go-6

Bump actions/setup-go from 5 to 6
…-commit_config

Add a configuration block for pre-commit.ci
Add a configuration to automatically label pull requests
…bels

Adjust the labels dependabot uses for GitHub Actions updates
…eck_logic

Adjust the logic used to check for GNU getopt in the `setup-env` script
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 5.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@v4...v5)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: '5'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
…s/checkout-5

Bump actions/checkout from 4 to 5
This is done automatically with the `pre-commit autoupdate` command.
A new rule, `MD059/descriptive-link-text`, was added in markdownlint's
0.38.0 release, which itself is used in v0.45.0 of markdownlint-cli. As
such, we must update to conform to the new rule.
jsf9k and others added 4 commits September 19, 2025 16:58
⚠️ CONFLICT! Lineage pull request for: skeleton
This adds labels that are common in downstream repositories to the core
configuration. This will help ensure consistent label availability.
Add a configuration to automatically apply the `docker` label to pull
requests.
Add more repository labels and expand the auto-labeling configuration
@cisagovbot cisagovbot added the upstream update This issue or pull request pulls in upstream updates label Sep 24, 2025
@github-actions github-actions bot added documentation This issue or pull request improves or adds to documentation dependencies Pull requests that update a dependency file github-actions Pull requests that update GitHub Actions code test This issue or pull request adds or otherwise modifies test code ansible Pull requests that update Ansible code labels Sep 25, 2025
@jsf9k jsf9k unassigned dav3r and mcdonnnj Sep 30, 2025
@jsf9k jsf9k marked this pull request as ready for review September 30, 2025 20:52
@jsf9k jsf9k enabled auto-merge September 30, 2025 20:52
@jsf9k jsf9k merged commit 2e43bc7 into develop Oct 1, 2025
50 checks passed
@jsf9k jsf9k deleted the lineage/skeleton branch October 1, 2025 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ansible Pull requests that update Ansible code dependencies Pull requests that update a dependency file documentation This issue or pull request improves or adds to documentation github-actions Pull requests that update GitHub Actions code test This issue or pull request adds or otherwise modifies test 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.

4 participants