-
Notifications
You must be signed in to change notification settings - Fork 2
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
⚠️ CONFLICT! Lineage pull request for: skeleton #25
Conversation
* Add instructions for cross-platform builds * Clean up shields * Clean up tables for each Docker configuration item * Add section about supported tags
This should resolve the following error: Error: Workflows triggered by Dependabot on the "push" event run with read-only access. Uploading Code Scanning results requires write access. To use Code Scanning with Dependabot, please ensure you are using the "pull_request" event for this workflow and avoid triggering on the "push" event for Dependabot branches. See https://docs.github.com/en/code-security/secure-coding/configuring-code-scanning#scanning-on-push for more information on how to configure these events.
Co-authored-by: Hillary <hillary.jeffrey@trio.dhs.gov>
Co-authored-by: Hillary <hillary.jeffrey@trio.dhs.gov>
Co-authored-by: Hillary <hillary.jeffrey@trio.dhs.gov>
Co-authored-by: Hillary <hillary.jeffrey@trio.dhs.gov>
Co-authored-by: Hillary <hillary.jeffrey@trio.dhs.gov>
Co-authored-by: Nick M. <50747025+mcdonnnj@users.noreply.github.com>
Co-authored-by: Hillary <hillary.jeffrey@trio.dhs.gov>
Co-authored-by: Hillary <hillary.jeffrey@trio.dhs.gov>
Co-authored-by: Hillary <hillary.jeffrey@trio.dhs.gov>
* Add a comment describing what the files does. * Add sections to organize patterns.
Due to her departure this removes hillaryj from the default CODEOWNERS we use in our projects.
The semver package is needed by the bump_version.sh script, but it is not included in requirements-dev.txt.
The version attribute has been depricated and will be removed once our systems move to a more recent release.
Co-authored-by: Hillary <hillary.jeffrey@trio.dhs.gov>
Since the GitHub Actions configuration builds images on tag pushes, we should use the standard tagging script we use for the same purpose in other repositories. This will make it easier to tag, build, and push Docker images of a specific version in a standardized manner.
Co-authored-by: Shane Frasier <jeremy.frasier@trio.dhs.gov>
Hooks updated with the `pre-commit autoupdate` command. Note: The `ansible-lint` hook is intentionally being held back on 4.3.7 because of ongoing issues with the 5.x version and how we use Ansible (standalone Galaxy roles).
With the release of pyenv v2.0.0 there is a breaking change around startup logic that necessitates an update for our pyenv setup instructions. Also add a statement about how to get configuration instructions from pyenv itself.
Update pre-commit Hooks
…owners Remove User from CODEOWNERS
…ctions Update Instructions for Configuring pyenv
Improve gitignore file comments and organization.
…-for-linting Install terraform and packer for the linting job
…_shfmt Replace beautysh hook with cisagov/pre-commit-shfmt
Update to reflect the new pre-commit configuration.
⚠️ CONFLICT! Lineage pull request for: skeleton
…onfiguration Standardize the Layout of the Lineage Configuration File
Update the Pin for actions/github-script to v4
Use preferred capitalization for Docker and Docker Hub
90722bb
to
46fceb1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work wrangling this beast! These docker repos are painful to update because of all the README.md
changes.
This all looks great to me, modulo the issues that @dav3r brought up.
a838bd7
to
3a938ac
Compare
The project does not rely on any underlying versioning to dictate the version used in its image tags. The README is updated to reflect that state of affairs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Git 'er dun! 🚜
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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-docker.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 conflictsthat 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
status
command. Fix any conflicts andpossibly incorrect auto-merges.
After resolving each of the conflicts,
add
your changes to thebranch,
commit
, andpush
your 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.
Check the "Everything is cool" checkbox below:
Mark this draft pull request "Ready for review".
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