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 #27

Merged
merged 21 commits into from
Aug 27, 2021
Merged

Conversation

felddy
Copy link
Member

@felddy felddy commented Aug 27, 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 git@github.com:cisagov/certboto-docker.git certboto-docker
    cd certboto-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 Dockerfile 
    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

dependabot bot and others added 20 commits July 5, 2021 17:01
Bumps python from 3.9-alpine to 3.9.6-alpine.

---
updated-dependencies:
- dependency-name: python
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Issue cisagov/skeleton-docker#69 has been created to remind us to
re-add it once it is again supported by the official Python Docker
image.
Instead of manually installing a Terraform binary we can leverage the Action
provided by Hashicorp to do the same thing.
This sets a specific rule for MD035 (Horizontal rule style) instead of the
default value of "consistent".
This sets a specific rule for MD046 (code block style) instead of the default
value of "consistent".
Update pre-commit hooks using `pre-commit autoupdate`. The `ansible-lint` hook
is intentionally held back due to issues with switching to v5.
Add markdownlint Rules to Enforce Specific Formatting
…n_gha_workflow

Use the hashicorp/setup-terraform Action to Install Terraform in GHA Workflow
This reverts commit 3ebf37d.

There was finally a successful build of the official Python Docker
image upstream, so we can add this back in.

Resolves cisagov/skeleton-docker#69.
Lineage pull request for: skeleton
…pine

Bump python from 3.9-alpine to 3.9.6-alpine
@felddy felddy added the upstream update This issue or pull request pulls in upstream updates label Aug 27, 2021
@jsf9k jsf9k marked this pull request as ready for review August 27, 2021 14:19
@jsf9k jsf9k merged commit d334efd into develop Aug 27, 2021
@jsf9k jsf9k deleted the lineage/skeleton branch August 27, 2021 17:04
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.

4 participants