Skip to content

Conversation

cisagovbot
Copy link

@cisagovbot cisagovbot commented Oct 6, 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-generic.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/skeleton-python-library.git skeleton-python-library
    cd skeleton-python-library
    git remote add skeleton https://github.com/cisagov/skeleton-generic.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 .github/labeler.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 5 commits October 3, 2025 10:04
We can enable all label configurations for actions/labeler by default
now that all of these labels are defined in the configuration for
crazy-max/ghaction-github-labeler.
…nfigurations

Enable all label configuration for `actions/labeler`
Add labels for JavaScript and TypeScript to the configuration for
crazy-max/ghaction-github-labeler.
Add the new `javascript` and `typescript` labels with appropriate
matching rules to the actions/labeler configuration.
Add JavaScript-related labels with labeling support
@cisagovbot cisagovbot added the upstream update This issue or pull request pulls in upstream updates label Oct 6, 2025
@jsf9k jsf9k unassigned dav3r and mcdonnnj Oct 7, 2025
@jsf9k jsf9k force-pushed the lineage/skeleton branch from 5e5c220 to a6eb87d Compare October 7, 2025 14:17
@jsf9k jsf9k marked this pull request as ready for review October 7, 2025 14:37
@jsf9k jsf9k requested review from dav3r, jsf9k and mcdonnnj as code owners October 7, 2025 14:37
@jsf9k jsf9k enabled auto-merge October 7, 2025 14:38
@jsf9k jsf9k moved this from In progress to Review in progress in Skeleton Maintenance Oct 7, 2025
@jsf9k jsf9k merged commit c29f4a0 into develop Oct 7, 2025
113 checks passed
@jsf9k jsf9k deleted the lineage/skeleton branch October 7, 2025 14:40
@github-project-automation github-project-automation bot moved this from Review in progress to Done in Skeleton Maintenance Oct 7, 2025
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
Development

Successfully merging this pull request may close these issues.

4 participants