Skip to content
This repository was archived by the owner on Dec 1, 2022. It is now read-only.

Conversation

cisagovbot
Copy link

@cisagovbot cisagovbot commented Jun 2, 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-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/skeleton-aws-lambda.git skeleton-aws-lambda
    cd skeleton-aws-lambda
    git remote add skeleton https://github.com/cisagov/skeleton-python-library.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 .gitignore 
    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 14 commits April 12, 2021 10:37
* 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.
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
Improve gitignore file comments and organization.
Lineage pull request for: skeleton
@cisagovbot cisagovbot added the upstream update This issue or pull request pulls in upstream updates label Jun 2, 2021
@mcdonnnj mcdonnnj force-pushed the lineage/skeleton branch from 9d31d21 to 44eed12 Compare June 4, 2021 14:24
@mcdonnnj mcdonnnj marked this pull request as ready for review June 4, 2021 14:32
@mcdonnnj mcdonnnj requested review from jsf9k and mcdonnnj as code owners June 4, 2021 14:32
Copy link
Member

@dav3r dav3r left a comment

Choose a reason for hiding this comment

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

🛴

@mcdonnnj mcdonnnj merged commit 9c2af76 into develop Jun 4, 2021
@mcdonnnj mcdonnnj deleted the lineage/skeleton branch June 4, 2021 20:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

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