chore: removing unused env attributes for CI workflow

.github/workflows/master.yml

@@ -36,10 +36,8 @@ jobs:
         GO_ENV: test
         MONGODB_URI: mongodb://127.0.0.1:27017
         MONGO_DB: switcher-gitops-test
-        SWITCHER_API_URL: ${{ secrets.SWITCHER_API_URL }}
-        SWITCHER_API_JWT_SECRET: ${{ secrets.SWITCHER_API_JWT_SECRET }}
-        GIT_TOKEN: ${{ secrets.GIT_TOKEN }}
         GIT_USER: ${{ secrets.GIT_USER }}
+        GIT_TOKEN: ${{ secrets.GIT_TOKEN }}
         GIT_TOKEN_READ_ONLY: ${{ secrets.GIT_TOKEN_READ_ONLY }}
         GIT_REPO_URL: ${{ secrets.GIT_REPO_URL }}
         GIT_BRANCH: ${{ secrets.GIT_BRANCH }}

README.md

@@ -23,27 +23,18 @@ GitOps Domain Snapshot Orchestrator for Switcher API
 **Switcher GitOps** is Domain Snapshot Orchestrator for Switcher API. It allows you to manage your feature flags and configurations in a GitOps manner. It is a simple and easy way to manage your feature flags and configurations in a versioned manner.
 
 # Features
-- Manage Switchers with GitOps driven environment
-- Multiple and independent Environments
+- Manage Switchers with GitOps managed environment
 - Auto Sync enables a fully integrated environment with Switcher API Management, Slack App and GitOps working simultaneously
 
 # Integrated tests
 
-This project does not run integration test without a valid GitOps repository settings.
-
-In order to run integration tests locally, you need to create a valid GitOps repository with the following structure:
-
-```bash
-├── resources
-│   ├── default.json (*)
-```
-(*) see a Switcher snapshot sample [here](https://github.com/switcherapi/switcher-gitops/blob/master/resources/default.json)
-
-The next step is to set up PAT (Personal Access Token) for Switcher GitOps to access the repository. You can either create a fine-grained token with only the necessary permissions such as Content (Read and Write) and Metadata (Read) or use a personal token with full access.
+Set up PAT (Personal Access Token) for Switcher GitOps to access the repository. You can either create a fine-grained token with only the necessary permissions such as Content (Read and Write) and Metadata (Read) or use a personal token with full access.
 
 Once you have the token, you can set it up in the `.env.test` environment file by including the following:
 ```bash
+GIT_USER=[YOUR_GIT_USER]
 GIT_TOKEN=[YOUR_GIT_TOKEN]
+GIT_TOKEN_READ_ONLY=[YOUR_GIT_TOKEN_READ_ONLY]
 GIT_REPO_URL=[YOUR_GIT_REPO_URL]
 GIT_BRANCH=[YOUR_GIT_BRANCH]
 ```