chore(ci): updating branch reference from master to develop(HEAD) (#384) (#385)

* chore(ci): updating branch reference from master to develop(HEAD) (#384)


Signed-off-by: mittachaitu <sai.chaithanya@mayadata.io>
Co-authored-by: sai chaithanya <sai.chaithanya@mayadata.io>

docs/backup-restore.md

@@ -53,7 +53,7 @@ We have to install the velero 1.5 or later version for ZFS-LocalPV.
 Deploy the minio for storing the backup :-
 
 ```
-$ kubectl apply -f https://raw.githubusercontent.com/openebs/zfs-localpv/master/deploy/sample/minio.yaml
+$ kubectl apply -f https://raw.githubusercontent.com/openebs/zfs-localpv/develop/deploy/sample/minio.yaml
 ```
 
 The above minio uses tmp directory inside the pod to store the data, so when restart happens, the backed up data will be gone. We can change the above yaml to use persistence storage to store the data so that we can persist the data after restart.

docs/developer-setup-examples.md

@@ -15,7 +15,7 @@ sudo dpkg -i minikube_1.9.2-0_amd64.deb
 sudo minikube start --driver=none
 sudo chown -R $USER $HOME/.kube $HOME/.minikube
 
-kubectl apply -f https://raw.githubusercontent.com/openebs/zfs-localpv/master/deploy/zfs-operator.yaml
+kubectl apply -f https://raw.githubusercontent.com/openebs/zfs-localpv/develop/deploy/zfs-operator.yaml
 kubectl get pods -n kube-system -l role=openebs-zfs
 
 export OPENEBS_NAMESPACE=openebs

docs/developer-setup.md

@@ -25,7 +25,7 @@ git clone https://github.com/$user/zfs-localpv.git
 cd zfs-localpv
 git remote add upstream https://github.com/openebs/zfs-localpv.git
 
-# Never push to upstream master
+# Never push to upstream develop
 git remote set-url --push upstream no_push
 
 # Confirm that your remotes make sense:
@@ -44,15 +44,15 @@ Open a terminal on your local host. Change directory to the zfs-localpv fork roo
 $ cd zfs-localpv
 ```
 
- Checkout the master branch.
+ Checkout the develop branch.
 
  ```sh
- $ git checkout master
- Switched to branch 'master'
- Your branch is up-to-date with 'origin/master'.
+ $ git checkout develop
+ Switched to branch 'develop'
+ Your branch is up-to-date with 'origin/develop'.
  ```
 
- Recall that origin/master is a branch on your remote GitHub repository.
+ Recall that origin/develop is a branch on your remote GitHub repository.
  Make sure you have the upstream remote openebs/zfs-localpv by listing them.
 
  ```sh
@@ -68,43 +68,43 @@ $ cd zfs-localpv
  ```sh
  $ git remote add upstream https://github.com/openebs/zfs-localpv.git
  ```
- Fetch all the changes from the upstream master branch.
+ Fetch all the changes from the upstream develop branch.
 
  ```sh
- $ git fetch upstream master
+ $ git fetch upstream develop
  remote: Counting objects: 141, done.
  remote: Compressing objects: 100% (29/29), done.
  remote: Total 141 (delta 52), reused 46 (delta 46), pack-reused 66
  Receiving objects: 100% (141/141), 112.43 KiB | 0 bytes/s, done.
  Resolving deltas: 100% (79/79), done.
  From github.com:openebs/zfs-localpv
-   * branch            master     -> FETCH_HEAD
+   * branch            develop     -> FETCH_HEAD
  ```
 
- Rebase your local master with the upstream/master.
+ Rebase your local develop with the upstream/develop.
 
  ```sh
- $ git rebase upstream/master
+ $ git rebase upstream/develop
  First, rewinding head to replay your work on top of it...
- Fast-forwarded master to upstream/master.
+ Fast-forwarded develop to upstream/develop.
  ```
- This command applies all the commits from the upstream master to your local master.
+ This command applies all the commits from the upstream develop to your local develop.
 
  Check the status of your local branch.
 
  ```sh
  $ git status
- On branch master
- Your branch is ahead of 'origin/master' by 38 commits.
+ On branch develop
+ Your branch is ahead of 'origin/develop' by 38 commits.
  (use "git push" to publish your local commits)
  nothing to commit, working directory clean
  ```
- Your local repository now has all the changes from the upstream remote. You need to push the changes to your own remote fork which is origin master.
+ Your local repository now has all the changes from the upstream remote. You need to push the changes to your own remote fork which is origin develop.
 
- Push the rebased master to origin master.
+ Push the rebased develop to origin develop.
 
  ```sh
- $ git push origin master
+ $ git push origin develop
  Username for 'https://github.com': $user
  Password for 'https://$user@github.com':
  Counting objects: 223, done.
@@ -112,16 +112,16 @@ $ cd zfs-localpv
  Writing objects: 100% (69/69), 8.76 KiB | 0 bytes/s, done.
  Total 69 (delta 53), reused 47 (delta 31)
  To https://github.com/$user/zfs-localpv.git
- 8e107a9..5035fa1  master -> master
+ 8e107a9..5035fa1  develop -> develop
  ```
 
 ### Contributing to a feature or bugfix. 
 
-Always start with creating a new branch from master to work on a new feature or bugfix. Your branch name should have the format XX-descriptive where XX is the issue number you are working on followed by some descriptive text. For example:
+Always start with creating a new branch from develop to work on a new feature or bugfix. Your branch name should have the format XX-descriptive where XX is the issue number you are working on followed by some descriptive text. For example:
 
  ```sh
- $ git checkout master
- # Make sure the master is rebased with the latest changes as described in previous step.
+ $ git checkout develop
+ # Make sure the develop is rebased with the latest changes as described in previous step.
  $ git checkout -b 1234-fix-developer-docs
  Switched to a new branch '1234-fix-developer-docs'
  ```
@@ -145,7 +145,7 @@ Happy Hacking!
 ```sh
 # While on your myfeature branch (see above)
 git fetch upstream
-git rebase upstream/master
+git rebase upstream/develop
 ```
 
 While you rebase your changes, you must resolve any conflicts that might arise and build and test your changes using the above steps. 

docs/faq.md

@@ -14,7 +14,7 @@ Go to each node and create the ZFS Pool, which will be used for provisioning the
 Once ZFS POOL is created we can install OpenEBS ZFS driver by running the following command.
 
 ```
-kubectl apply -f https://raw.githubusercontent.com/openebs/zfs-localpv/master/deploy/zfs-operator.yaml
+kubectl apply -f https://raw.githubusercontent.com/openebs/zfs-localpv/develop/deploy/zfs-operator.yaml
 ```
 
 Verify that the ZFS driver Components are installed and running using below command :
@@ -37,7 +37,7 @@ openebs-zfs-node-twmx8     2/2     Running   0          5h28m
 
 ### 3. How to upgrade the driver to newer version
 
-Follow the instructions here https://github.com/openebs/zfs-localpv/tree/master/upgrade.
+Follow the instructions here https://github.com/openebs/zfs-localpv/tree/develop/upgrade.
 
 ### 4. ZFS Pools are there on certain nodes only, how can I create the storage class.
 

docs/grafana-dashboard.md

@@ -105,7 +105,7 @@ prometheus-operator-prometheus-node-exporter   ClusterIP   10.98.128.115   <none
 - Paste the below json and Click on Load
 
   ```
-  https://raw.githubusercontent.com/openebs/zfs-localpv/master/deploy/sample/grafana-dashboard.json
+  https://raw.githubusercontent.com/openebs/zfs-localpv/develop/deploy/sample/grafana-dashboard.json
   ```
 - Select datasource as Prometheus and Import it.
 
@@ -121,7 +121,7 @@ This dashboard exposes below metrics
 
 The "ZFS-LocalPV" dashboard will look like this :-
 
-![Grafana](https://github.com/openebs/zfs-localpv/blob/master/deploy/sample/vol-stats.png)
+![Grafana](https://github.com/openebs/zfs-localpv/blob/develop/deploy/sample/vol-stats.png)
 
 ## References:
 - https://helm.sh/docs/intro/install/