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: piceaTech/node-gitlab-2-github
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: Cynical-Optimist/node-gitlab-2-github
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.
  • 14 commits
  • 5 files changed
  • 2 contributors

Commits on Oct 9, 2020

  1. replace usernames with links

    replace usernames mentioned in issues, pull requests and comments, with
    a link pointing back to the original gitlab user. The link text makes it
    clear that it points to a gitlab user and not a github user.
    
    This occurs regardless of what's in usermap in the settings. usermap is
    now only useful for assigning issues and pull requests to users.
    Cynical-Optimist committed Oct 9, 2020
    Configuration menu
    Copy the full SHA
    ce79222 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    19a84cf View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    8268f8e View commit details
    Browse the repository at this point in the history
  4. don't assign issues or PRs to anyone

    Disable assignments altogether. The script shouldn't attempt to set
    assignees on issues and pull requests. Instead, we will add them
    manually.
    
    Note that "usermap" in settings will now be completely unused.
    Cynical-Optimist committed Oct 9, 2020
    Configuration menu
    Copy the full SHA
    16c0962 View commit details
    Browse the repository at this point in the history

Commits on Oct 12, 2020

  1. Merge pull request #6 from Cynical-Optimist/dwinship/replace-username…

    …s-with-links
    
    replace usernames with links
    Douglas Winship
    Douglas Winship authored Oct 12, 2020
    Configuration menu
    Copy the full SHA
    8c78bfa View commit details
    Browse the repository at this point in the history
  2. Merge pull request #7 from Cynical-Optimist/dwinship/only-transfer-op…

    …en-MRs
    
    only transfer open MRs: never migrate MR as issues
    Douglas Winship
    Douglas Winship authored Oct 12, 2020
    Configuration menu
    Copy the full SHA
    a1c037f View commit details
    Browse the repository at this point in the history
  3. Merge pull request #8 from Cynical-Optimist/dwinship/link-back-to-git…

    …lab-issues-or-merge-requests
    
    add links back to original issue or merge request
    Douglas Winship
    Douglas Winship authored Oct 12, 2020
    Configuration menu
    Copy the full SHA
    8697067 View commit details
    Browse the repository at this point in the history
  4. Merge pull request #9 from Cynical-Optimist/dwinship/dont-assign-issu…

    …es-or-pull-requests
    
    don't assign issues or PRs to anyone
    Douglas Winship
    Douglas Winship authored Oct 12, 2020
    Configuration menu
    Copy the full SHA
    fa6e1e4 View commit details
    Browse the repository at this point in the history

Commits on Oct 13, 2020

  1. skip non-open merge requests completely

    don't produce any message claiming that an MR is being processed, unless
    it is an open MR. (Only open MRs are processed and transferred, now)
    Cynical-Optimist committed Oct 13, 2020
    Configuration menu
    Copy the full SHA
    e2e86ee View commit details
    Browse the repository at this point in the history
  2. don't check for issues with same name as MRs

    previously, a Merge Request would not be migrated if an issue existed
    with the same name. This was because Merge Requests could be migrated as
    issues, and the goal was to avoid duplicates.
    However, there were too many false positives.
    Merge Requests are now no longer migrated as issues anyway, so this
    check is being removed.
    Cynical-Optimist committed Oct 13, 2020
    Configuration menu
    Copy the full SHA
    1c2aae0 View commit details
    Browse the repository at this point in the history
  3. don't create the gitlab merge request label

    merge requests are no longer being migrated as issues under any
    circumstances, so this is an uneccesary label.
    Cynical-Optimist committed Oct 13, 2020
    Configuration menu
    Copy the full SHA
    5adcc6a View commit details
    Browse the repository at this point in the history

Commits on Oct 19, 2020

  1. Merge pull request #10 from Cynical-Optimist/dwinship/abort-non-open-…

    …mr-transfers-earlier
    
    Don't even attempt MR migrations unless the MR is open
    Douglas Winship
    Douglas Winship authored Oct 19, 2020
    Configuration menu
    Copy the full SHA
    c171c6d View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    2725435 View commit details
    Browse the repository at this point in the history
  3. Merge pull request #11 from Cynical-Optimist/dwinship/update-README

    Update README and sample_settings
    Douglas Winship
    Douglas Winship authored Oct 19, 2020
    Configuration menu
    Copy the full SHA
    6947001 View commit details
    Browse the repository at this point in the history
Loading