renamed default branch to main

.github/workflows/codeql-analysis.yml

@@ -2,10 +2,10 @@ name: "CodeQL"
 
 on:
   push:
-    branches: [master, ]
+    branches: [main, ]
   pull_request:
     # The branches below must be a subset of the branches above
-    branches: [master]
+    branches: [main]
   schedule:
     - cron: '0 2 * * 6'
 

.github/workflows/cron-update.yml

@@ -4,7 +4,7 @@ on:
   schedule:
     - cron: '0 10 * * 5' # everyday at 10am
   push:
-    branches: [master, ]
+    branches: [main, ]
 
 jobs:
   vendor-update:

.github/workflows/deploy-pages.yml

@@ -2,7 +2,7 @@ name: GitHub Pages
 
 on:
   push:
-    branches: [master, ]
+    branches: [main, ]
   schedule:
     - cron: '0 2 * * 6'
 

CONTRIBUTING.md

@@ -13,7 +13,7 @@ resources to make it easier to get your contribution accepted.
 
 This is a rough outline of what a contributor's workflow looks like:
 
-- Create a topic branch from where you want to base your work. This is usually master.
+- Create a topic branch from where you want to base your work. This is usually main.
 - Make commits of logical units and add test case if the change fixes a bug or adds new functionality.
 - Run tests and make sure all the tests are passed.
 - Make sure your commit messages are in the proper format (see below).

test/README.md

@@ -2,12 +2,12 @@
 
   Here we provide several test samples. Though the original PCAP files are not uploaded due to restrictions on file size of GitHub, you may still easily get a simple but thorough view of `pcapkit`, either on how to use it or on what it can do.
 
- - [`test_extraction`](https://github.com/JarryShaw/pcapkit/tree/master/test/test_extraction.py) -- samples on usage of `pcapkit.extract`, which extracts a PCAP file and dumps to a specificly formatted output file
- - [`test_ipv6`](https://github.com/JarryShaw/pcapkit/tree/master/test/test_ipv6.py) -- samples on extraction of IPv6 packets, whilst dumping a tree-view text file
- - [`test_http`](https://github.com/JarryShaw/pcapkit/tree/master/test/test_http.py) -- samples on extraction of HTTP packets, whilst checking if HTTP is `in` the frame
- - [`test_reassembly`](https://github.com/JarryShaw/pcapkit/tree/master/test/test_reassembly.py) -- samples on reassembly of TCP payloads, whilst writing the reassembled payloads into an output file
- - [`test_analyse`](https://github.com/JarryShaw/pcapkit/tree/master/test/test_analyse.py) -- samples on analysis of application layer after reassembly, which writes the extracted HTTP frame to `stdout`
- - [`test_time`](https://github.com/JarryShaw/pcapkit/tree/master/test/test_time.py) -- samples on a minimum usage of `pcapkit.extract`, whilst timing the whole procedure
- - [`test_trace`](https://github.com/JarryShaw/pcapkit/tree/master/test/test_trace.py) -- samples on tracing TCP flows
- - [`test_engine`](https://github.com/JarryShaw/pcapkit/tree/master/test/test_engine.py) -- samples on different extraction engines
- - [`test_profile`](https://github.com/JarryShaw/pcapkit/tree/master/test/test_profile.py) -- samples on performance analysis of `pcapkit`
+ - [`test_extraction`](https://github.com/JarryShaw/pcapkit/tree/main/test/test_extraction.py) -- samples on usage of `pcapkit.extract`, which extracts a PCAP file and dumps to a specificly formatted output file
+ - [`test_ipv6`](https://github.com/JarryShaw/pcapkit/tree/main/test/test_ipv6.py) -- samples on extraction of IPv6 packets, whilst dumping a tree-view text file
+ - [`test_http`](https://github.com/JarryShaw/pcapkit/tree/main/test/test_http.py) -- samples on extraction of HTTP packets, whilst checking if HTTP is `in` the frame
+ - [`test_reassembly`](https://github.com/JarryShaw/pcapkit/tree/main/test/test_reassembly.py) -- samples on reassembly of TCP payloads, whilst writing the reassembled payloads into an output file
+ - [`test_analyse`](https://github.com/JarryShaw/pcapkit/tree/main/test/test_analyse.py) -- samples on analysis of application layer after reassembly, which writes the extracted HTTP frame to `stdout`
+ - [`test_time`](https://github.com/JarryShaw/pcapkit/tree/main/test/test_time.py) -- samples on a minimum usage of `pcapkit.extract`, whilst timing the whole procedure
+ - [`test_trace`](https://github.com/JarryShaw/pcapkit/tree/main/test/test_trace.py) -- samples on tracing TCP flows
+ - [`test_engine`](https://github.com/JarryShaw/pcapkit/tree/main/test/test_engine.py) -- samples on different extraction engines
+ - [`test_profile`](https://github.com/JarryShaw/pcapkit/tree/main/test/test_profile.py) -- samples on performance analysis of `pcapkit`