Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: ilkka/git-https-push-action
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: utrustdev/git-https-push-action
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 4 commits
  • 3 files changed
  • 1 contributor

Commits on Jun 15, 2022

  1. Update Alpine image to version 3.16 (#1)

    Why:
    We're using this action for a while (3 years) and it is still being built based on a outdated alpine version. A docker scan showed that it has a critical vulnerability that it's fixed on later versions.
    Screenshot 2022-06-15 at 18 05 51
    More info: https://security.snyk.io/vuln/SNYK-ALPINE310-APKTOOLS-1534688
    
    Doing the same scan when using alpine:3.16 showed no known vulnerabilities.
    Screenshot 2022-06-15 at 18 07 46
    
    Also, since the action has no changes for a while, it's best if we keep doing security updates while we still use it.
    
    This addresses the issue by:
    - Update docker container alpine:3.10 to alpine:3.16 (latest ATOW)
    nunoapfernandes authored Jun 15, 2022
    Configuration menu
    Copy the full SHA
    d6a7ae9 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    45fe9ff View commit details
    Browse the repository at this point in the history

Commits on Jul 4, 2022

  1. Update git config to set directory as safe (#3)

    Why:
    
    Previous configuration was breaking.
    nunoapfernandes authored Jul 4, 2022
    Configuration menu
    Copy the full SHA
    dc668ba View commit details
    Browse the repository at this point in the history

Commits on Jul 28, 2022

  1. Attempt to merge changes from heroku before pushing new version (#4)

    Why:
    When trying to push changes to heroku, sometimes it gets stuck because there are some changes made from someone else besides this action which means that it needs to merge those changes to the branch its trying to push. We only want to manage deploys via this action so there's no need to be careful when pushing changes to heroku.
    
    This addresses the issue by:
    - Adding --force to git push so it is always able to deploy.
    nunoapfernandes authored Jul 28, 2022
    Configuration menu
    Copy the full SHA
    77d09e1 View commit details
    Browse the repository at this point in the history
Loading