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.

Sign up for GitHub

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

Jump to bottom

Use Actions git context instead of dynamically created buildkit one (#25381) #25383

Merged
merged 2 commits into from
Jun 20, 2023
Merged

Use Actions git context instead of dynamically created buildkit one (#25381) #25383

merged 2 commits into from
Jun 20, 2023

Commits on Jun 20, 2023

  1. Use Actions git context instead of dynamically created buildkit one (g… 

    …o-gitea#25381)

The [docker/build-push-action@v2
action](https://github.com/docker/build-push-action) by default ignores
the checkout created using the actions/checkout@v2 action. When you pass
a git build context to docker build, it wouldn't include the .git
directory.

By passing `context: .` to the build step then it'll use the Actions git
context which includes the git fetch from the earlier step.
    @techknowlogick @GiteaBot
    techknowlogick authored and GiteaBot committed Jun 20, 2023
    Configuration menu
    Copy the full SHA
    0b742c9 View commit details
    Browse the repository at this point in the history

  2. Merge branch 'release/v1.20' into backport-25381-v1.20

    @GiteaBot
    GiteaBot authored Jun 20, 2023
    Configuration menu
    Copy the full SHA
    c71920e View commit details
    Browse the repository at this point in the history