Merge pull request #51 from andi-bigswitch/bsc-17548-rm-bionic

BSC-16720 BSC-17548 - remove Ubuntu 18.04 bionic from build matrix and rename master refs to main

.github/workflows/run-tests.yml

@@ -1,18 +1,18 @@
 name: Run Tests
 on:
   workflow_dispatch: # Allows this workflow to be manually triggered
-  push:  # Run for every push to and PR filed against master
-    branches: [ master ]
+  push:  # Run for every push to and PR filed against main (renamed from master)
+    branches: [ main ]
   pull_request:
-    branches: [ master ]
+    branches: [ main ]
   schedule:
     - cron: "0 0 * * *" # At the end of every day
 jobs:
   build:
     runs-on: ${{ matrix.os-version }}
     strategy:
       matrix:
-        os-version: [ubuntu-18.04, ubuntu-20.04, ubuntu-latest]
+        os-version: [ubuntu-20.04, ubuntu-latest]
         python-version:
           - "3.6"
           - "3.7"

CONTRIBUTING.md

@@ -31,11 +31,11 @@ When you're done making changes and you'd like to propose them for review, use t
 Congratulations! The pybsn community thanks you. :sparkles:
 
 ### How to release a new version of pybsn
-To help release a new version of pybsn, there are two github actions. They are triggered when a new tag is pushed to the repository. Each tag push is considered a release, and each of the two actions will attempt to create a release using the version found in [setup.py](https://github.com/bigswitch/pybsn/blob/master/setup.py). The name of the tag does not matter from a technical perspective, but should match the version in the `setup.py` file. 
-1. [release-github.yml](https://github.com/bigswitch/pybsn/blob/master/.github/workflows/release-github.yml) 
-Creates a release on github. The release description is the message of the last commit of the release branch (`master`).
-2. [release-pypi.yml](https://github.com/bigswitch/pybsn/blob/master/.github/workflows/release-pypi.yml) 
+To help release a new version of pybsn, there are two github actions. They are triggered when a new tag is pushed to the repository. Each tag push is considered a release, and each of the two actions will attempt to create a release using the version found in [setup.py](https://github.com/bigswitch/pybsn/blob/main/setup.py). The name of the tag does not matter from a technical perspective, but should match the version in the `setup.py` file.
+1. [release-github.yml](https://github.com/bigswitch/pybsn/blob/main/.github/workflows/release-github.yml)
+Creates a release on github. The release description is the message of the last commit of the release branch (`main`).
+2. [release-pypi.yml](https://github.com/bigswitch/pybsn/blob/main/.github/workflows/release-pypi.yml)
 Creates a release on [PyPi](https://pypi.org/project/pybsn/).
 
 ### Attribution
-This `CONTRIBUTING.md` has been adapted from [Github Docs](https://github.com/github/docs/blob/main/CONTRIBUTING.md).
+This `CONTRIBUTING.md` has been adapted from [Github Docs](https://github.com/github/docs/blob/main/CONTRIBUTING.md).