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

Draft
wants to merge 488 commits into
base: develop
Choose a base branch
from

Conversation

cisagovbot
Copy link

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/cyhy-commander-docker.git cyhy-commander-docker
    cd cyhy-commander-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 .github/dependabot.yml README.md 
    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

@cisagovbot cisagovbot added the upstream update This issue or pull request pulls in upstream updates label Nov 22, 2022
@jsf9k jsf9k assigned felddy, jasonodoom, dav3r and mcdonnnj and unassigned jsf9k Dec 6, 2023
mcdonnnj and others added 16 commits January 19, 2024 06:04
This will run the Go tool `goimports` against the repository if it
contains any Go files. This tool bundles the functionality of `go fmt`
with the additional benefit of sorting Go imports much like the isort
tool we use for Python code.
This is a temporary fix until @mcdonnnj has
his PR approved and merged into the terraform-docs
repo. This fix will perform a shallow clone of his
forked branch, build the binary, and install it.
PATH is handled by `setup-go` so we can refactor the code setting it. Also we are taking advantage of the -C switch to handle building from the cloned repository.

Co-authored-by: Nick <[email protected]>
`TODO` was placed on the wrong comment block. Also I am adding a link to the issue for the TODO.
This commit is introducing 2 new flags
into the setup-env script. -l or
--list-versions will list available
Python versions and allow the user to
select a version interactively. The second
flag -v or --version will allow a user
to set the version if installed.
(e.g. ./setup-env -v 3.9.6)
This makes the code a bit cleaner and still accomplishes the same functionality

Co-authored-by: Shane Frasier <[email protected]>
If the Python version exists then we want the script to continue
execution.
pyenv local is run below.
If PYTHON_VERSION is an empty string then the system Python will be used.
mcdonnnj and others added 30 commits February 3, 2025 01:37
This will explicitly define the name for the Compose project.
Ensure that all of the keys in the Compose file are sorted
alphabetically.
The value for the `published` key in a `ports` definition is expected
to be a string.
Using `compose` instead of `docker-compose` is now the preferred
default for Docker Compose files.
Remove functionality to create special buildx Dockerfile
…mver-pin

Add a comment explaining why we pin `semver`
Use the peter-evans/dockerhub-description Action to update the Docker
Hub description instead of a bash script.
Instead of updating the description whenever the `build` workflow is
run we will only update the description on `push` events to the
`develop` branch. This will ensure that only approved edits are pushed
to Docker Hub.
…r_hub_update

Use a GitHub Action to update the Docker Hub description
This replaces a nonexistent input name with the valid one.
Correct input to the `peter-evans/dockerhub-description` Action
Bump the following package versions:
- pip from 24.3.1 to 25.0.1
- pipenv from 2024.4.0 to 2024.4.1
- setuptools from 75.6.0 to 75.8.0
Update the dependencies installed in the Python virtual environment by
running `pipenv lock` in the `src/` directory.
Instead of comparing the project version and the version read from the
container log directly as strings it makes sense to parse them and
contextually compare them. This is important if you are comparing, for
example, a Python package version that should match the Docker image,
but the Docker image has a build identifier (ex: `1.0.0` and
`1.0.0+build.1`). The version should be considered equivalent in this
scenario if a project is properly following SemVer versioning.
…on_comparisons

Use the `semver` package to parse the log version in testing
Instead of overriding the context and file we can allow the Action to
fall back on its default behaviour of using the `git` context to pull
the source needed to build the image. This also allows us to remove the
actions/checkout Action from the `build` and `build-push-all` jobs.
This instructs prettier to ignore `*.lock` files since they are just
JSON files and will be formatted by the pretty-format-json hook.
…ld_jobs

Use `docker/build-push-action` default behavior
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.

7 participants