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

Lineage pull request for: skeleton #12

Merged
merged 3 commits into from
Aug 18, 2023
Merged

Lineage pull request for: skeleton #12

merged 3 commits into from
Aug 18, 2023

Conversation

cisagovbot
Copy link

@cisagovbot cisagovbot commented Aug 17, 2023

Lineage Pull Request

Lineage has created this pull request to incorporate new changes found in an
upstream repository:

Upstream repository: https://github.com/cisagov/skeleton-docker.git
Remote branch: HEAD

Check the changes in this pull request to ensure they won't cause issues with
your project.

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

  • 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 July 20, 2023 01:49
The pytest-dockerc plug is unmaintained and there is now a dependency
issues with PyYAML because of the release of Cython v3 (which is itself
a build dependency for PyYAML). After some research this seemed like
the most similar package in terms of functionality to the package we
are replacing. Although it is not a pytest plugin it still provides
similar access and uses the Docker composition defined in the
repository.
Switch packages used to test the configuration
@cisagovbot cisagovbot added the upstream update This issue or pull request pulls in upstream updates label Aug 17, 2023
@dav3r
Copy link
Member

dav3r commented Aug 18, 2023

I don't think the tests will all pass here until the first-commits PR (#5) is merged.

Copy link
Member

@mcdonnnj mcdonnnj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dav3r I vote we approve and merge this PR because it's only failing when it gets to pushing to the GitHub Container Registry. The failure is to be expected because it's still under the cisagov/example namespace until #5 is merged, and that PR cannot pass tests until the changes in this PR are merged.

@dav3r
Copy link
Member

dav3r commented Aug 18, 2023

@dav3r I vote we approve and merge this PR because it's only failing when it gets to pushing to the GitHub Container Registry. The failure is to be expected because it's still under the cisagov/example namespace until #5 is merged, and that PR cannot pass tests until the changes in this PR are merged.

Agreed. The old 🐔 and 🥚 conundrum strikes again!

@jsf9k jsf9k merged commit 974564e into develop Aug 18, 2023
9 of 10 checks passed
@jsf9k jsf9k deleted the lineage/skeleton branch August 18, 2023 18:33
@mcdonnnj mcdonnnj mentioned this pull request Aug 18, 2023
12 tasks
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