⚠️ CONFLICT! Lineage pull request for: skeleton

[cisagovbot]

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-python-library.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/tpt-reports.git tpt-reports
   cd tpt-reports
   git remote add skeleton https://github.com/cisagov/skeleton-python-library.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/dependabot.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

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!

• [x] ✌️ The conflicts in this pull request have been resolved.
• [x] All relevant type-of-change labels have been added.
• [x] All new and existing tests pass.

✅ Pre-merge checklist

Remove any of the following that do not apply. These boxes should remain unchecked until the pull request has been approved.

• [x] Bump major, minor, patch, or pre-release version as appropriate via the bump_version.sh script if this repository is versioned and the changes in this PR warrant a version bump.

✅ Post-merge checklist

Remove any of the following that do not apply.

• [ ] Create a release.

---

[!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

[coveralls]

Pull Request Test Coverage Report for Build 7302046105

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 0.0%

---

Totals
Change from base Build 7183864213:	0.0%
Covered Lines:	0
Relevant Lines:	0

---

💛 - Coveralls

[jsf9k]

I had already resolved the conflicts and this PR was just awaiting review. @schmelz21, why did you close it?

[schmelz21]

@jsf9k, that was my misunderstanding then. I went through the conflict resolution steps and believe an auto-merge / delete pr occured. I will stay away from the future lineage PRs when they come in. I can see the file changes now in this PR. https://github.com/cisagov/tpt-reports/pull/80

[jsf9k]

See #80, which was created by Lineage after this PR was closed.

[jsf9k]

@jsf9k, that was my misunderstanding then. I went through the conflict resolution steps and believe an auto-merge / delete pr occured. I will stay away from the future lineage PRs when they come in. I can see the file changes now in this PR. #80

No problem. I just thought that maybe it was intentional and I was missing something.