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: typescript-eslint/typescript-eslint
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.25.0
Choose a base ref
...
head repository: typescript-eslint/typescript-eslint
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.26.0
Choose a head ref
  • 10 commits
  • 39 files changed
  • 6 contributors

Commits on Mar 23, 2020

  1. Configuration menu
    Copy the full SHA
    258fdd0 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    b1b8284 View commit details
    Browse the repository at this point in the history

Commits on Mar 26, 2020

  1. Configuration menu
    Copy the full SHA
    4fa7107 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    638d84d View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    7d963fd View commit details
    Browse the repository at this point in the history

Commits on Mar 27, 2020

  1. Configuration menu
    Copy the full SHA
    1e29e69 View commit details
    Browse the repository at this point in the history

Commits on Mar 28, 2020

  1. Configuration menu
    Copy the full SHA
    f3160b4 View commit details
    Browse the repository at this point in the history

Commits on Mar 30, 2020

  1. chore: separate linting checks to their own step (#1801)

    If linting/formatting/spelling fails, it should not block running the tests.
    If they do block, they can increase the iteration time for contributors, because they will have to fix them before they can see the status of their tests.
    
    By not blocking, a contributor will be able to submit a PR, and come back ~5min later knowing they will be able to see if their code passes linting _and_ tests.
    
    This should also knock ~40-60s off of the perceived runtime, as it parallelises some of the work.
    bradzacher authored Mar 30, 2020
    Configuration menu
    Copy the full SHA
    bfdffb4 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    543bc79 View commit details
    Browse the repository at this point in the history
  3. chore: publish v2.26.0

    JamesHenry committed Mar 30, 2020
    Configuration menu
    Copy the full SHA
    151f89b View commit details
    Browse the repository at this point in the history
Loading