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: TheKevJames/coveralls-python
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 2.2.0
Choose a base ref
...
head repository: TheKevJames/coveralls-python
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 3.0.0
Choose a head ref
  • 6 commits
  • 5 files changed
  • 3 contributors

Commits on Jan 12, 2021

  1. docs(github): fixes env var flag details (#244)

    Details:
    
    * The docs section 'Github Actions Gotcha' stated that the COVERALLS_FLAG_NAME
      env var is needed in order to avoid 'pile up of jobs'. It turns out that
      it is optional, and when specified, can be specified with the same value
      across all jobs or with unique values.
      This change clarifies that in the documentation.
    
    * This change also clarifies that the COVERALLS_REPO_TOKEN env var is not needed
      for GitHub Actions.
    
    * This change also renames the heading of the section to 'Github Actions support'
      to have a more neutral name.
    
    Signed-off-by: Andreas Maier <andreas.r.maier@gmx.de>
    andy-maier authored Jan 12, 2021
    Configuration menu
    Copy the full SHA
    14cea5a View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    05b66aa View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    db523ff View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    6ebdc5e View commit details
    Browse the repository at this point in the history
  5. feat(config): reorder configuration precedence (#249)

    We've been getting a slew of cases where users are reporting requiring
    different configurations -- especially Github Actions, where we seem to
    need to set a different service name on a case-by-case basis.
    
    Reordering our configuration precedence such that user-specified values
    overwrite the CI defaults should allow users to fix these problems
    without requiring a one-size-fits-all code change.
    
    This is massively backwards incompatible for anyone with the same key
    set to two different values in their configs.
    TheKevJames authored Jan 12, 2021
    Configuration menu
    Copy the full SHA
    f4faa92 View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    209a13a View commit details
    Browse the repository at this point in the history
Loading