⚠️ CONFLICT! Lineage pull request for: skeleton#158
Merged
Conversation
These collections are required for the amazon.aws.aws_ssm lookup plugin and the community.general.json_query filter.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: jsf9k <5521725+jsf9k@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Add some missing collections
Correct terraform-docs step name and comment to reference cisagov branch
Also remove any roles that are not used here.
In both cases the boilerplate language does not apply for this project.
jsf9k
approved these changes
Mar 4, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This Lineage-generated sync PR pulls in upstream “skeleton” changes to keep this repository’s dependency/install plumbing aligned with the shared CISAGov template, particularly around Ansible collection usage.
Changes:
- Document
boto3as required due to use ofamazon.aws.s3_object. - Add required Ansible collections (
amazon.aws,community.general) toansible/requirements.yml. - Update the GitHub Actions lint workflow to install both Ansible roles and collections.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
requirements.txt |
Updates commentary explaining why boto3 is included. |
ansible/requirements.yml |
Introduces explicit Ansible collection requirements alongside roles. |
.github/workflows/build.yml |
Installs Ansible roles and collections during the lint job. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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-packer.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
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