Skip to content
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

⚠️ CONFLICT! Lineage pull request for: skeleton #3

Merged
merged 4 commits into from
Mar 24, 2025

Conversation

cisagovbot
Copy link

@cisagovbot cisagovbot commented Mar 21, 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-action-composite.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-disable-apparmor.git action-disable-apparmor
    cd action-disable-apparmor
    git remote add skeleton https://github.com/cisagov/skeleton-action-composite.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 action.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 3 commits March 11, 2025 19:23
These options mirror our defaults for workflows and represent the
common guardrails we have in our bash scripts.
…ell_argument

Add options for the `shell` parameter
@cisagovbot cisagovbot added the upstream update This issue or pull request pulls in upstream updates label Mar 21, 2025
@jsf9k jsf9k force-pushed the lineage/skeleton branch from a534829 to be81a0c Compare March 21, 2025 18:01
@jsf9k jsf9k marked this pull request as ready for review March 21, 2025 18:03
@jsf9k jsf9k requested a review from a team March 21, 2025 18:03
@jsf9k jsf9k enabled auto-merge March 21, 2025 18:32
@jsf9k jsf9k merged commit b777e77 into develop Mar 24, 2025
4 checks passed
@jsf9k jsf9k deleted the lineage/skeleton branch March 24, 2025 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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