⚠️ CONFLICT! Lineage pull request for: skeleton#899
Conversation
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
These comments have been left in other downstream projects so we should restore them here for consistency.
073f201 to
6917d80
Compare
There was a problem hiding this comment.
Pull Request Overview
This is a lineage pull request that incorporates upstream changes from the skeleton-generic repository, specifically adding Docker label support and improving configuration comments. The PR had merge conflicts that have been resolved.
- Added Docker label configuration to support Docker-related pull requests
- Enhanced labeler configuration with clarifying comments for different technology stacks
- Resolved merge conflicts as indicated by the "CONFLICT!" title
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/labels.yml | Added new Docker label definition for Docker-related pull requests |
| .github/labeler.yml | Added Docker labeler configuration (commented out) and clarifying comments for technology stack sections |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
jsf9k
left a comment
There was a problem hiding this comment.
Do you need to update the version tags for cisagov/setup-env-github-action, actions/setup-python, and actions/checkout here? Aren't those part of the upstream changes?
Since this descends directly from cisagov/skeleton-generic those changes were already merged during the last top-level wave in #896. |
Lineage Pull Request: CONFLICT
Lineage has created this pull request to incorporate new changes found in an upstream repository:
Upstream repository:
https://github.com/cisagov/skeleton-generic.gitRemote branch:
HEADCheck the changes in this pull request to ensure they won't cause issues with your project.
The
lineage/skeletonbranch has one or more unresolved merge conflicts that you must resolve before merging this pull request!How to resolve the conflicts
Take ownership of this pull request by removing any other assignees.
Clone the repository locally, and reapply the merge:
Review the changes displayed by the
statuscommand. Fix any conflicts and possibly incorrect auto-merges.After resolving each of the conflicts,
addyour changes to the branch,commit, andpushyour changes: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.
Wait for all the automated tests to pass.
Confirm each item in the "Pre-approval checklist" below.
Remove any of the checklist items that do not apply.
Ensure every remaining checkbox has been checked.
Mark this draft pull request "Ready for review".
✅ Pre-approval checklist
Remove any of the following that do not apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!
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