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

⚠️ CONFLICT! Lineage pull request for: skeleton #25

Merged
merged 109 commits into from
Aug 10, 2021
Merged

Conversation

cisagovbot
Copy link

@cisagovbot cisagovbot commented Jun 3, 2021

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 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 [email protected]:cisagov/postfix-docker.git postfix-docker
    cd postfix-docker
    git remote add skeleton https://github.com/cisagov/skeleton-docker.git
    git remote set-url --push skeleton no_push
    git switch develop
    git checkout -b 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 README.md docker-compose.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. Check the "Everything is cool" checkbox below:

    • ✌️ The conflicts in this pull request have been resolved.
  7. 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

felddy and others added 30 commits March 25, 2021 17:37
* Duplicates DockerHub tags for ghcr.io
* Adds login to GitHub Container Registry using the GITHUB_TOKEN secret.
* Documentation update to reflect multi-registry publication.
* 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 <[email protected]>
Co-authored-by: Hillary <[email protected]>
Co-authored-by: Hillary <[email protected]>
Co-authored-by: Hillary <[email protected]>
Co-authored-by: Hillary <[email protected]>
Co-authored-by: Nick M. <[email protected]>
Co-authored-by: Hillary <[email protected]>
Co-authored-by: Hillary <[email protected]>
Co-authored-by: Hillary <[email protected]>
* 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 <[email protected]>
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 <[email protected]>
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.
…ctions

Update Instructions for Configuring pyenv
jsf9k and others added 18 commits July 19, 2021 13:03
…-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
# Conflicts:
#	.github/lineage.yml
#	.github/workflows/build.yml
Update the Pin for actions/github-script to v4
Use preferred capitalization for Docker and Docker Hub
# Conflicts:
#	README.md
#	tests/conftest.py
"username" is changed to "user" in this function to work around a CodeQL 
failure for "Clear-text logging of sensitive information".
@dav3r dav3r requested review from mcdonnnj and removed request for hillaryj August 6, 2021 14:09
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.

:shipit:

@dav3r dav3r merged commit 55b367b into develop Aug 10, 2021
@dav3r dav3r deleted the lineage/skeleton branch August 10, 2021 19:43
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