neetob 0.1.4 → 0.1.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 341391d50e6f4be4c69fe7608c6cdcdad8ffecb7fbf55aac1bdcf0fa307a51dd
-  data.tar.gz: 2984a090795cf1f51a05e8dfd18957ba74172469f432cef6f8f217f2739dbbf2
+  metadata.gz: 641eee79e8d05537132030cc9db2ca8d4a57e60e480552dcb1a904fd00e542f5
+  data.tar.gz: a4c674222429b42cff84e1eeb7a66212b32da60f4248a36a4dae5b03439cc649
 SHA512:
-  metadata.gz: e2f7b80a100686409a27f851aa9abc9f74bcbe101ebe6a635619bd9c6a5db9e8ed39804444207f63703db4e207a7f886272117a6287c8cfc3421ac3ba81dde3a
-  data.tar.gz: 19ca0f250839ef5c0c47ec51520fbdfd7af5ae344e9efedbefb6f8a9579c4675307f0a11a50a029de83709f2ba02ce8f0017e3814289719c09289f5a6b8676fd
+  metadata.gz: 57951a8d15b4514b7468b7994094c42ff8b0786f6dee034091db26b71d909094c90235855f208a1b1bbc1cc4125add4a53afb6869e82e255baadbe22846220a7
+  data.tar.gz: e47da7744b3a4d92aa23881673f88d6cd9e1b795d92ddb67d0be5676229b82ea194b43125d0f8904bbf009c054f52884d1e5e43e2ecdff4d06eccea9e6bf227b

data/.rubocop.yml

@@ -1,6 +1,6 @@
 # cspell:Disable
 AllCops:
-  TargetRubyVersion: 3.0.4
+  TargetRubyVersion: 3.1.3
   # RuboCop has a bunch of cops enabled by default. This setting tells RuboCop
   # to ignore them, so only the ones explicitly set in this file are enabled.
   DisabledByDefault: true

data/.ruby-version

@@ -1 +1 @@
-3.0.4
+3.1.3

data/.semaphore/semaphore.yml

@@ -9,7 +9,7 @@ global_job_config:
   prologue:
     commands:
       - checkout
-      - sem-version ruby 3.0.4
+      - sem-version ruby 3.1.3
       - bundle config path 'vendor/bundle'
       - bundle install
   env_vars:

data/CHANGELOG.md

@@ -1,5 +1,12 @@
 ## [Unreleased]
 
+### [0.1.5](https://www.github.com/bigbinary/neetob/compare/v0.1.4...v0.1.5) (2023-03-01)
+
+
+### Bug Fixes
+
+* handled some edge cases in the update and upsert labels cmd ([#192](https://www.github.com/bigbinary/neetob/issues/192)) ([dc87d19](https://www.github.com/bigbinary/neetob/commit/dc87d198a6a22850f3e04659413bed41d9db454f))
+
 ### [0.1.4](https://www.github.com/bigbinary/neetob/compare/v0.1.3...v0.1.4) (2023-02-23)
 
 

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    neetob (0.1.4)
+    neetob (0.1.5)
       dotenv (~> 2.8.1)
       launchy (~> 2.5.0)
       octokit (~> 4.0)
@@ -237,6 +237,7 @@ GEM
 
 PLATFORMS
   x86_64-darwin-21
+  x86_64-darwin-22
   x86_64-linux
 
 DEPENDENCIES

data/README.md

@@ -1,12 +1,13 @@
 # neetob
 
-The `neetob` gem gives different commands for interacting with Github repos and Heroku instances of existing neeto products, nanos and [repos](https://github.com/bigbinary/neeto-compliance/blob/main/data/neeto_repos.json).
+The `neetob` gem gives different commands for interacting with Github repos, Heroku instances and other tools to manage the workflow of neeto products.
 
 ## Table of Contents
 
-1. [Getting Started](#getting-started)
-   1. [Installation](#installation)
-2. [Usage](#usage)
+1. [Usage](#usage)
+   1. [Installing neetob for use](#installing-neetob-for-use)
+   2. [For development](#for-development)
+2. [Source of truth](#source-of-truth)
 3. [Working with GitHub](#working-with-github)
    1. [Issues](#issues)
    2. [Labels](#labels)
@@ -21,36 +22,22 @@ The `neetob` gem gives different commands for interacting with Github repos and
 5. [Working with Users](#working-with-users)
    1. [Audit](#audit)
    2. [Commits](#commits)
-6. [Working with Make Repos Uptodate](#working-with-make-repos-uptodate)
+6. [Make Repos Uptodate](#make-repos-uptodate)
 7. [Working with local Repos](#working-with-local-repos)
    1. [ls](#ls)
 8. [Testing](#testing)
 
-## Getting started
-
-### Installation
-
-Clone the repository onto your system using the following command:
-
-```sh
-git clone https://github.com/bigbinary/neetob.git
-```
-
-Navigate to the root of the application directory.
+## Usage
 
-```sh
-cd neetob
-```
+### Installing neetob for use
 
-To set up `neetob`, execute the below command from the root of the application directory.
+Install and update the gem using the following command:
 
 ```sh
-bin/setup
+gem install neetob && gem update neetob
 ```
 
-## Usage
-
-Utilize the `help` keyword to access a comprehensive list of all the available commands and options.
+Use the `help` keyword to access a list of all the available commands and options.
 
 ```
 neetob help
@@ -66,9 +53,7 @@ Options:
   [--sandbox] # All the commands in sandbox mode will run only on the "neeto-dummy" app.
 ```
 
-**By default, all commands will be executed in non-sandbox mode.**
-
-### Useful command-line options
+#### Useful command-line options
 
 | Option       | Meaning                           |
 | ------------ | --------------------------------- |
@@ -77,11 +62,85 @@ Options:
 | --no-sandbox | Non-Sandbox mode                  |
 | --help       | Provides information on a command |
 
-**Note:** The commands within `neetob` should be used with caution, as improper usage may result in unintended consequences, and some actions may not be reversible.
+The commands within `neetob` should be used with caution, as improper usage may result in unintended consequences, and some actions may not be reversible. By default, all commands will be executed in non-sandbox mode.
+
+### For development
+
+Clone the repository onto your system using the following command:
+
+```sh
+git clone https://github.com/bigbinary/neetob.git
+```
+
+Navigate to the root of the application directory.
+
+```sh
+cd neetob
+```
+
+To check and use the latest changes in the local repository install `neetob` like so:
+
+```sh
+bin/setup
+```
+
+We can use, check or debug the `neetob` locally by directly invoking the `neetob` class like so:
+
+```sh
+ruby exe/neeetob
+```
+
+#### Conventional commit messages
+
+In `neetob` we are using the Google's [release please](https://github.com/googleapis/release-please) Github action to auto update the version and release the latest gem.
+
+In order to make this action work we have to use the [conventional commit messages](https://www.conventionalcommits.org/en/v1.0.0/).
+
+The Conventional commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history.
+
+Generally, we use three types of suffix in the commit messages that are as follows:
+
+1. `fix:` for the commit that fixes a bug in the codebase. This updates the third digit in the version. For example, `0.1.0` version will be updated to `0.1.1`.
+
+2. `feat:` for the commit that introduces a new feature to the codebase. This updates the second digit in the version. For example, `0.1.0` version will be updated to `0.2.0`.
+
+3. `BREAKING CHANGE:` for the commit that introduces a breaking API change. This updates the first digit in the version. For example, `0.1.0` version will be updated to `1.0.0`.
+
+For more details please refer [official docs](https://www.conventionalcommits.org/en/v1.0.0/) from Conventional commits.
+
+In `neetob` we use "squash and merge" option while merging the PR. So we have to update the commit message while squash and merge so that Github action can track that merge commit.
+
+For example:
+
+![Commit message update](images/commit-message-update.png)
+
+## Source of truth
+
+This [list of repos](https://github.com/bigbinary/neeto-compliance/blob/main/data/neeto_repos.json) is used as the "source of truth".
+
+## Passing list of heroku apps as option
+
+`neetob` allows you to pass list of apps in the following three formats.
+
+```
+// all staging heroku instances
+--apps "neeto-*-staging"
+
+// all production heroku instances
+--apps "neeto-*-production"
+
+// all staging and production instances
+--apps "neeto-*-web"
+
+// for local testing
+--apps neeto-dummy
+```
+
+For safety reasons all the examples given below would be using `--apps neeto-*-staging`.
 
 ## Working with GitHub
 
-Efficiently gain access to a comprehensive list of all the available subcommands for the `github` command by utilizing the `help` keyword.
+Check the list of all the available subcommands for the `github` command by utilizing the `help` keyword.
 
 ```sh
 neetob github help
@@ -91,10 +150,11 @@ neetob github help
 
 ```sh
 # Lists and counts all the open issues that are currently unassigned
-neetob github issues list --count --state open --assignee none --apps "neeto-*-web"
+neetob github issues list --count --state open --assignee none --apps "neeto-*-staging"
 
 # Lists, counts and filters all unassigned open issues that are labeled as "bug"
-neetob github issues list --count --label bug --state open --assignee none --apps "neeto-*-web"
+neetob github issues list --count --label bug --state open --assignee none \
+--apps "neeto-*-staging"
 ```
 
 ### Labels
@@ -103,10 +163,10 @@ The `labels` command provides an interface for interacting with Github labels.
 
 ```sh
 # Lists the details of all the labels in the Github repo
-neetob github labels list --apps "neeto-*-web"
+neetob github labels list --apps "neeto-*-staging"
 
 # Provides the details for a specific label in the Github repo
-neetob github labels show --name priority --apps "neeto-*-web"
+neetob github labels show --name priority --apps "neeto-*-staging"
 
 # Changes the name of the label
 neetob github labels update --old-name "High Priority" --new-name \
@@ -116,20 +176,19 @@ neetob github labels update --old-name "High Priority" --new-name \
 neetob github labels upsert --all-neeto-repos
 
 # Accepts a different JSON file using `path` option
-neetob github labels upsert --path ~/Desktop/labels.json --apps "neeto-*-web"
+neetob github labels upsert --path ~/Desktop/labels.json --apps "neeto-*-staging"
 
-# The `upsert` command can also upsert a single label using `name`, `color`
-# and `description` options
+# Upsert a single label using `name`, `color`, and `description` options
 # No `#` is required while adding `color`
 neetob github labels upsert --name UI --color 8250df --description \
 "UI work needed" --all-neeto-repos
 
 # Deletes the given labels from the Github repos
 neetob github labels delete --labels "High Priority" "Priority 1" "bug" \
---apps "neeto-*-web"
+--apps "neeto-*-staging"
 
 # Deletes all the labels from the Github repos
-neetob github labels delete_all --apps "neeto-*-web"
+neetob github labels delete_all --apps "neeto-*-staging"
 ```
 
 Check out the default labels [file](data/github-labels.json) for the required JSON file structure.
@@ -150,7 +209,7 @@ Don't use `#` before the color code.
 Searches for keywords across multiple neeto projects within specified files by utilizing the `search` command.
 
 ```sh
-neetob github search --keyword neeto --path README.md --apps "neeto-*-web"
+neetob github search --keyword neeto --path README.md --apps "neeto-*-staging"
 ```
 
 ### Protect branch
@@ -158,7 +217,7 @@ neetob github search --keyword neeto --path README.md --apps "neeto-*-web"
 Updates branch protection rules in neeto repos by using the `protect_branch` command.
 
 ```sh
-neetob github protect_branch --branch main --apps neeto-dummy
+neetob github protect_branch --branch main --apps "neeto-*-staging"
 ```
 
 By default, file "data/branch-protection-rules.json" will be used for updating the branch protection rules.
@@ -224,37 +283,37 @@ neetob heroku help
 
 ### Config vars
 
-The `config_vars` command is useful to interact with Heroku config variables.
+The `config_vars` command interacts with Heroku config variables.
 
 ```sh
 # The `list` command lists all the Heroku config variables
-neetob heroku config_vars list --apps "neeto-*-production"
+neetob heroku config_vars list --apps "neeto-*-staging"
 
-# We can list specific Heroku config variables using `keys` option
-neetob heroku config_vars list --apps "neeto-*-production" --keys key1 key2  key3
+# List specific Heroku config variables using `keys` option
+neetob heroku config_vars list --apps "neeto-*-staging" --keys key1 key2  key3
 
-# We can also use a file to specify required config vars for `list` command
-# Checkout the `data/config-vars-list.json` file for the required structure.
-neetob heroku config_vars list --apps "neeto-*-production" --path \
+# List specific Heroku config variables using a file
+# Checkout the `data/config-vars-list.json` file for the required structure
+neetob heroku config_vars list --apps "neeto-*-staging" --path \
 neetob/data/config-vars-list.json
 
-# The `audit` command will check the config variables against the JSON file named as
+# The `audit` command checks the config variables against the JSON file named as
 # `required-config-vars.json` that is present inside the `data` directory at the root of
-# installed `neetob` gem.
-neetob heroku config_vars audit --apps "neeto-*-production"
+# installed `neetob` gem
+neetob heroku config_vars audit --apps "neeto-*-staging"
 
-# The `audit` command can also be used with a different JSON file using `--path` option.
-neetob heroku config_vars audit --path ~/Desktop/config.json --apps "neeto-*-production"
+# The `audit` command also works with a different JSON file using `--path` option
+neetob heroku config_vars audit --path ~/Desktop/config.json --apps "neeto-*-staging"
 
-# The `upsert` command adds or updates the config variables from the
-# `data/config-vars-upsert.json` file present at the root of installed `neetob` gem.
+# The `upsert` command adds or updates config variables from the
+# `data/config-vars-upsert.json` file present at the root of installed `neetob` gem
 neetob heroku config_vars upsert --apps "neeto-*-staging"
 
-# The `remove` command is used to delete `config_vars`.
+# The `remove` command deletes config variables
 neetob heroku config_vars remove --keys=TEST_KEY_1 TEST_KEY_2 --apps "neeto-*-staging"
 ```
 
-We can use a custom JSON file with `upsert` command using the `path` option.
+We can use a custom JSON file with `upsert` command using the `--path` option.
 
 For example, assume we have a file named `config.json` on the Desktop, like so:
 
@@ -266,13 +325,13 @@ For example, assume we have a file named `config.json` on the Desktop, like so:
 }
 ```
 
-To update the above-mentioned config variables to all staging apps, we can use the upsert command like so:
+To update the above-mentioned config variables to all staging apps, we can use the `upsert` command like so:
 
 ```sh
 neetob heroku config_vars upsert --path ~/Desktop/config.json --apps "neeto-*-staging"
 ```
 
-The `upsert` command can also be used to update and insert project-specific config variables.
+The `upsert` command can also update or insert project-specific config variables.
 
 For example, assume we have a file named `config.json` on the `Desktop` with the following properties:
 
@@ -293,79 +352,75 @@ For example, assume we have a file named `config.json` on the `Desktop` with the
 To update the above-mentioned config variables under the defined project, we can use the upsert command like so:
 
 ```sh
-neetob heroku config_vars upsert --path_with_project_keys ~/Desktop/config.json
+neetob heroku config_vars upsert --path_with_project_keys ~/Desktop/config.json --apps "neeto-*-staging"
 ```
 
 ### Access
 
-We can list, add, and remove users from multiple Heroku apps using the `access` command.
+The `access` command list, add and remove users from multiple Heroku apps.
 
 ```sh
-# The `list` command retrieves a list of all the users from Heroku apps.
-neetob heroku access list --apps "neeto-*-production"
+# List all the users from Heroku apps
+neetob heroku access list --apps "neeto-*-staging"
 
-# Add new users to the Heroku apps.
+# Add new users to the Heroku apps
 neetob heroku access add --users oliver@bigbinary.com eve@bigbinary.com --apps "neeto-*-staging"
 
-# Remove the users from the Heroku apps.
+# Remove the users from the Heroku apps
 neetob heroku access remove --users oliver@bigbinary.com eve@bigbinary.com --apps \
 "neeto-*-staging"
 ```
 
 ### Execute
 
-Utilize the `execute` command to run a Heroku CLI command or a Rails console command for multiple neeto apps in one go.
+The `execute` command executes a Heroku CLI command or a Rails console command for multiple neeto apps in one go.
 
 ```sh
-# We can check who has access to the neeto Heroku apps like so:
-neetob heroku execute -c "heroku access" --apps "neeto-*-production"
+# Execute Heroku CLI command
+neetob heroku execute -c "heroku access" --apps "neeto-*-staging"
 
-# We can run a command in the Rails console for different neeto Heroku apps like so:
+# Execute Rails console command
 neetob heroku execute -c "Sidekiq::Cron::Job.destroy \"server_side_worker\"" --apps \
 "neeto-*-staging" --rails
 ```
 
 ## Working with users
 
-Using the `users` command, we can interact with the contributors of neeto applications.
+The `users` command interacts with the contributors of neeto applications.
 
 ### Audit
 
-The `audit` command enables the ability to comprehensively audit contributors across all neeto applications by providing functionality to check for contributors with multiple emails and users with third-party domain emails.
-
-This command will search and use the neeto repos in the current working directory.
-To fetch and update all neeto repos execute [make_repos_uptodate](#working-with-make-repos-uptodate) command before the `audit` command.
+The `audit` command checks the contributors across all neeto applications for multiple emails and third-party domain emails.
 
 ```sh
+# Audit all the contributors
 neetob users audit
 ```
 
 ### Commits
 
-Using `commits` command we can list the commits for a user in a defined duration.
+The `commits` command lists the commits for a user in a defined duration.
 
 ```sh
 # The below mentioned command will open a list of all the commits across neeto
-# product repos made by "udai1931" in the duration of last 6 months.
+# product repos made by "udai1931" in the duration of last 6 months
 neetob users commits --author udai1931 --duration 6.months
 
-# We can list commits for a specific product using `--apps` option.
+# List commits for a specific product using `--apps` option
 neetob users commits --author udai1931 --duration 6.months --apps neeto-kb-web
 
-# We can list commits for all neeto repos using the `--all-neeto-repos` option.
+# List commits for all neeto repos using the `--all-neeto-repos` option
 neetob users commits --author udai1931 --duration 6.months --all-neeto-repos
 ```
 
-## Working with Make Repos Uptodate
+## Make Repos Uptodate
 
-Using the `make_repos_uptodate` command, we can uptodate all neeto repos.
-The list of neeto repos is picked up from [neeto_compliance](https://github.com/bigbinary/neeto-compliance/blob/main/lib/neeto_compliance/neeto_repos.rb).
+The `make_repos_uptodate` command updates all neeto repos.
 
 ```sh
 neetob make_repos_uptodate
 
-# We have a `--all-neeto-repos` option for this command too so that we can
-# fetch and update all the neeto repos in the current working directory.
+# Update all neeto repos with `--all-neeto-repos`
 neetob make_repos_uptodate --all-neeto-repos
 ```
 
@@ -379,25 +434,21 @@ neeto-kb-web
 
 ## Working with local Repos
 
-Using the `local` command, we can interact with the local neeto repos.
+The `local` command interacts with the local neeto repos.
 
 ### ls
 
-The `ls` command can list the files from all the local neeto repos.
-
-This command will search and use the neeto repos in the current working directory.
-To fetch and update all neeto repos execute [make_repos_uptodate](#working-with-make-repos-uptodate) command before the `ls` command.
+The `ls` command lists the files from all the local neeto repos.
 
 ```sh
-# The `ls` command will list all the files in the root directory of neeto repos.
-neetob local ls --apps "*"
+# List all the files in the root directory of neeto repos
+neetob local ls --apps "neeto-*-web"
 
-# The `ls` command can also list files in a specific directory using the
-# `--dir` option.
-neetob local ls --dir public --apps "*"
+# List files in a specific directory with `--dir` option
+neetob local ls --dir public --apps "neeto-*-web"
 
-# We can also list files in a nested directory.
-neetob local ls --dir app/controllers --apps "*"
+# List files in a nested directory
+neetob local ls --dir app/controllers --apps "neeto-*-web"
 ```
 
 ## Testing

data/bookmarks.md

@@ -3,3 +3,28 @@
 [All UX issues](https://github.com/issues?q=is%3Aopen+is%3Aissue+org%3Abigbinary+label%3Aux)
 
 [Engineer needed](https://github.com/issues?q=is%3Aopen+is%3Aissue+org%3Abigbinary+label%3Aengineer-needed)
+
+- [ ] neeto-chat-web
+- [ ] neeto-desk-web
+- [ ] neeto-kb-web
+- [ ] neeto-invoice-web
+- [ ] neeto-form-web
+- [ ] neeto-cal-web
+- [ ] neeto-planner-web
+- [ ] neeto-course-web
+- [ ] neeto-runner-web
+- [ ] neeto-social-web
+- [ ] neeto-wireframe-web
+- [ ] neeto-changelog-web
+- [ ] neeto-quiz-web
+- [ ] neeto-site-web
+- [ ] neeto-crm-web
+- [ ] neeto-replay-web
+- [ ] neeto-invisible-web
+- [ ] neeto-testify-web
+- [ ] neeto-deploy-web
+- [ ] neeto-bugtrap-web
+- [ ] neeto-sign-web
+- [ ] neeto-monitor-web
+- [ ] neeto-ci-web
+- [ ] neeto-git-web

data/data/github-labels.json

@@ -44,11 +44,6 @@
     "description": "The issue has been reviewed and considered a valid issue.",
     "color": "A2D9CE"
   },
-  {
-    "name": "backend",
-    "description": "Deals with Ruby & Rails code majorly.",
-    "color": "C2E0C6"
-  },
   {
     "name": "bug",
     "description": "Something isn't working.",
@@ -106,37 +101,62 @@
   },
   {
     "name": "epic",
-    "description": "Will get closed when sub-issues fixed and this issue tracked in monthly milestone.",
+    "description": "Will get closed when sub-issues are fixed and this issue is tracked in a monthly milestone.",
     "color": "6A5ACD"
   },
+  {
+    "name": "backend",
+    "description": "Deals with Ruby & Rails code majorly.",
+    "color": "C2E0C6"
+  },
   {
     "name": "frontend",
-    "description": "Deals with JS(React or JS configs etc) code majorly.",
+    "description": "Deals with JS(React or JS configs etc) code majorly. It can also include UI fixes without the help of the UI team.",
     "color": "C2E0C6"
   },
+  {
+    "name": "UI",
+    "description": "UI/CSS work needed.",
+    "color": "8250df"
+  },
+  {
+    "name": "UX",
+    "description": "UX design needed.",
+    "color": "366FB9"
+  },
+  {
+    "name": "fullstack",
+    "description": "This issue is not just frontend or backend but it's fullstack",
+    "color": "D0ECE7"
+  },
   {
     "name": "high-priority",
     "description": "Urgent fix required. Should be done within a day at max.",
     "color": "B60205"
   },
   {
-    "name": "honeybadger",
-    "description": "Issue created by honeybadger.",
-    "color": "D3D3D3"
+    "name": "priority",
+    "description": "Means I am waiting for this issue to be fixed in order to take care of other issues.",
+    "color": "BA080D"
   },
   {
     "name": "low-priority",
     "description": "Other open issues can be taken up before this one.",
     "color": "BFDADC"
   },
+  {
+    "name": "honeybadger",
+    "description": "Issue created by honeybadger.",
+    "color": "D3D3D3"
+  },
   {
     "name": "neeto*-dependent",
-    "description": "This issue depends upon some other issue from neeto engines/frontend packages.",
+    "description": "This issue depends upon some other issue from nano (engines/frontend packages).",
     "color": "E54D82"
   },
   {
     "name": "on-hold",
-    "description": "Reason should be specified as a comment before putting issue/PR on-hold.",
+    "description": "The issue is on hold as per provided reason. The reason should be specified as a comment before putting the issue/PR on-hold.",
     "color": "E54D82"
   },
   {
@@ -154,11 +174,6 @@
     "description": "The issue has a PR associated with it.",
     "color": "D4C5F9"
   },
-  {
-    "name": "priority",
-    "description": "Means I am waiting for this issue to be fixed in order to take care of other issues.",
-    "color": "BA080D"
-  },
   {
     "name": "refactoring",
     "description": "Code changes, better way to organize code etc.",
@@ -169,21 +184,11 @@
     "description": "Vulnerabilities, security concerns etc.",
     "color": "BA080D"
   },
-  {
-    "name": "UI",
-    "description": "UI/CSS work needed.",
-    "color": "8250df"
-  },
   {
     "name": "UI-weekly-milestone",
-    "description": "This issue is part of the UI weekly milestone.",
+    "description": "This issue is part of the currently ongoing UI weekly milestone.",
     "color": "F9D0C4"
   },
-  {
-    "name": "UX-design-needed",
-    "description": "This issue is part of the UI weekly milestone.",
-    "color": "366FB9"
-  },
   {
     "name": "engineer-needed",
     "description": "Engineer is needed to work on the issue",
@@ -191,7 +196,22 @@
   },
   {
     "name": "working",
-    "description": "This issue is part of the UI weekly milestone.",
+    "description": "A branch associated with this issue is created.",
     "color": "D0ECE7"
+  },
+    {
+    "name": "product-analysis",
+    "description": "This issue is related to product analysis",
+    "color": "D0ECE7"
+  },
+  {
+    "name": "manual-qa-needed",
+    "description": "Manual QA is needed to verify the changes.",
+    "color": "CCDDCD"
+  },
+  {
+    "name": "manual-qa-completed",
+    "description": "Manual QA team has finished verifying the changes.",
+    "color": "CCDDCD"
   }
 ]

data/lib/neetob/cli/github/auth.rb

@@ -41,7 +41,7 @@ module Neetob
         end
 
         def request_authorization
-          post(uris["auth_req"], params: { client_id: client_id, scope: scope })
+          post(uris["auth_req"], params: { client_id:, scope: })
         end
 
         private
@@ -87,9 +87,9 @@ module Neetob
               res = post(
                 uris["token_req"],
                 params: {
-                  client_id: client_id,
+                  client_id:,
                   device_code: auth_data[:device_code],
-                  grant_type: grant_type
+                  grant_type:
                 }
               )
 

data/lib/neetob/cli/github/labels/update.rb

@@ -25,15 +25,25 @@ module Neetob
             matching_apps = find_all_matching_apps(apps, :github, sandbox, false, all_neeto_repos)
             matching_apps.each do |app|
               ui.info("\n Updating label for #{app} repo \n")
-              update_label!(app, old_name, new_name)
+              begin
+                update_label!(app, old_name, new_name)
+              rescue StandardError => e
+                ExceptionHandler.new(e).process
+              end
             end
           end
 
           private
 
             def update_label!(app, old_name, new_name)
+              client.label(app, new_name)
+              ui.error("Label with name \"#{new_name}\" already exists.")
+              nil
+            rescue Octokit::NotFound
               client.update_label(app, old_name, { name: new_name })
               ui.success("Label \"#{old_name}\" updated to \"#{new_name}\" successfully")
+            rescue StandardError => e
+              ExceptionHandler.new(e).process
             end
         end
       end

data/lib/neetob/cli/github/labels/upsert.rb

@@ -77,6 +77,8 @@ module Neetob
                   app, label_details["name"], label_details["color"] || WHITE_COLOR_HEX_CODE,
                   label_details)
                 ui.success("Label \"#{label_details["name"]}\" created successfully")
+              rescue StandardError => e
+                ExceptionHandler.new(e).process
               end
             end
 

data/lib/neetob/cli/ui.rb

@@ -18,7 +18,7 @@ module Neetob
       end
 
       def ask(question, echo = true)
-        shell.ask(question, echo: echo)
+        shell.ask(question, echo:)
       end
 
       def yes?(question)

data/lib/neetob/cli/users/commits.rb

@@ -156,7 +156,7 @@ module Neetob
             begin
               commits = client.commits(
                 app, "main",
-                { author: author, since: since_duration(duration), per_page: 100, page: page })
+                { author:, since: since_duration(duration), per_page: 100, page: })
             rescue => exception
               ui.error(exception.message)
               commits = []

data/lib/neetob/exception_handler.rb

@@ -26,7 +26,9 @@ module Neetob
       when Octokit::UnprocessableEntity
         ui.error(
           "Failed to complete the given request."\
-          " Make sure that the given entity is correct and processable")
+          " Make sure that the given entity is correct and processable"\
+          "#{exception.message}."
+        )
       when Octokit::Unauthorized
         ui.error(
           "You are unauthorized to make API calls,"\

data/lib/neetob/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Neetob
-  VERSION = "0.1.4"
+  VERSION = "0.1.5"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: neetob
 version: !ruby/object:Gem::Version
-  version: 0.1.4
+  version: 0.1.5
 platform: ruby
 authors:
 - Udai Gupta
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2023-02-23 00:00:00.000000000 Z
+date: 2023-03-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: thor
@@ -107,6 +107,7 @@ files:
 - data/config-vars-upsert.json
 - data/github-labels.json
 - exe/neetob
+- images/commit-message-update.png
 - install.sh
 - lib/neetob.rb
 - lib/neetob/cli.rb
@@ -179,7 +180,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.2.33
+rubygems_version: 3.3.26
 signing_key: 
 specification_version: 4
 summary: Provides a set of helper scripts for Github and Heroku.