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: kiegroup/git-backporting
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v4.5.0
Choose a base ref
...
head repository: kiegroup/git-backporting
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v4.5.1
Choose a head ref
  • 8 commits
  • 28 files changed
  • 5 contributors

Commits on Jan 11, 2024

  1. build(deps): bump follow-redirects from 1.15.2 to 1.15.4 (#92)

    Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.15.2 to 1.15.4.
    - [Release notes](https://github.com/follow-redirects/follow-redirects/releases)
    - [Commits](follow-redirects/follow-redirects@v1.15.2...v1.15.4)
    
    ---
    updated-dependencies:
    - dependency-name: follow-redirects
      dependency-type: indirect
    ...
    
    Signed-off-by: dependabot[bot] <[email protected]>
    Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
    dependabot[bot] authored Jan 11, 2024
    Copy the full SHA
    b7df1f8 View commit details

Commits on Feb 20, 2024

  1. fix: --no-squash on single-commit GitLab MR (#93)

    Due to off-by-one error in GitLabMapper, --no-squash was not effective
    on an MR containing single commit. Fix by using the same condition as
    GitHubMapper.
    peat-psuwit authored Feb 20, 2024
    Copy the full SHA
    300fa91 View commit details
  2. build: upgrade release-it (#94)

    lampajr authored Feb 20, 2024
    Copy the full SHA
    d4dc510 View commit details

Commits on Feb 23, 2024

  1. fix: --auth when --git-user contains space (#95)

    Since --git-user is a user-facing name, it's common to include a space
    in it. As such, it's not suitable to use as a username in a Git remote
    URL.
    
    GitLab documented that it doesn't (yet?) check for username [1], and
    from my testing GitHub doesn't seem to care either. So just use an
    arbitrary name as a username.
    
    [1] https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html
    peat-psuwit authored Feb 23, 2024
    Copy the full SHA
    9bcd6e6 View commit details
  2. chore: add issue templates and improve pr template (#99)

    lampajr authored Feb 23, 2024
    Copy the full SHA
    5afc464 View commit details
  3. build: skip ci when not required (#100)

    lampajr authored Feb 23, 2024
    Copy the full SHA
    2c5c546 View commit details
  4. fix(gh-96): fix git token parsing (#98)

    lampajr authored Feb 23, 2024
    Copy the full SHA
    c57fca6 View commit details
  5. chore: release v4.5.1 (#101)

    Co-authored-by: Create or Update Pull Request Action <[email protected]>
    github-actions[bot] and Create or Update Pull Request Action authored Feb 23, 2024
    Copy the full SHA
    bce5dd4 View commit details
Loading