Main

.circleci/config.yml

@@ -53,11 +53,11 @@ jobs:
  pip install codecov-cli
  - run:
  name: Run Predictor Analysis
- # Comparing the current commit (HEAD) to Lowest Common Ancestor with master (BASE)
+ # Comparing the current commit (HEAD) to Lowest Common Ancestor with main (BASE)
  # In practice this will be the base of the branch (almost all the time)
  command: |
  . venv/bin/activate
- codecovcli label-analysis --token=$STATIC_TOKEN --base-sha=$(git merge-base HEAD^ master)
+ codecovcli label-analysis --token=$STATIC_TOKEN --base-sha=$(git merge-base HEAD^ main)
  - run:
  name: Upload smart-labels
  command: |
@@ -91,7 +91,7 @@ jobs:
  pip install setuptools_rust mutmut[patch]
  pip install -r tests/requirements.txt
  python setup.py develop
- git diff master $CIRCLE_SHA1 > data.patch
+ git diff main $CIRCLE_SHA1 > data.patch
  mutmut run --use-patch-file data.patch || true
  mkdir /tmp/artifacts;
  mutmut junitxml > /tmp/artifacts/mut.xml

README.md

@@ -31,8 +31,8 @@ To release a new version, you need to:
  - You can check the latest version on https://github.com/codecov/shared/releases
  - As a rule of thumb, just add one to the micro version (number most to the right)
 2) Create a new PR:
-- Changing the `version` field on https://github.com/codecov/shared/blob/master/setup.py#L12 to that new version
-- Change https://github.com/codecov/shared/blob/master/CHANGELOG.md unreleased header name to that version, and create a new _unreleased_ section with the same subsections.
+- Changing the `version` field on https://github.com/codecov/shared/blob/main/setup.py#L12 to that new version
+- Change https://github.com/codecov/shared/blob/main/CHANGELOG.md unreleased header name to that version, and create a new _unreleased_ section with the same subsections.
 3) Merge that PR
 4) Create a new release on https://github.com/codecov/shared/releases/new