Ft verification email validation #23

kennyg37 · 2024-05-24T13:22:42Z

What does this PR do?

configures an automatic email as soon as a user signs up and validates the user using a jwt token connected to
a link in the email

Describe your changes

added a controller file to handle the token verification after the link is clicked

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Tests
[ ] Other

How should this be manually tested?

What are the relevant pivotal tracker stories?

Pivotal Tracker Link

Screenshots (if is appropriate)

Initial commit: Set up empty Node.js Express application structure an…

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

mugishaj092

generateVerificationToken function it's not necessary you can reuse generateToken and add tests

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

GabrielDushime

Good

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

gitguardian · 2024-05-27T17:08:13Z

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound

Some files could not be reviewed due to errors:

Oops! Something went wrong! :(
ESLint: 4.19.1.
ESLint couldn't find the plugin "eslint-plugin-@typescript-eslint". This can happen for a couple different reasons:
1. If ESLint is installed globally, then make sure eslint-plugin-@typescript-eslint is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.
2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
    npm i eslint-plugin-@typescript-eslint@latest --save-dev
If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

hound · 2024-06-03T10:36:19Z

src/database/config/config.js

+    dialectModule: pg,
+  },
+  production: {
+    url: `postgres://${process.env.PRO_DB_USER}:${process.env.PRO_DB_PASS}@${process.env.PRO_DB_HOST}/${process.env.PRO_DB_NAME}`,


'template literal syntax' is only available in ES6 (use 'esversion: 6').

hound · 2024-06-03T10:36:19Z

src/database/config/config.js

+    },
+  },
+  test: {
+    url: `postgres://${process.env.TEST_DB_USER}:${process.env.TEST_DB_PASS}@${process.env.TEST_DB_HOST}/${process.env.TEST_DB_NAME}`,


'template literal syntax' is only available in ES6 (use 'esversion: 6').

hound · 2024-06-03T10:36:19Z

src/database/config/config.js

+
+module.exports = {
+  development: {
+    url: `${process.env.DB_URL}`,


'template literal syntax' is only available in ES6 (use 'esversion: 6').

hound · 2024-06-03T10:36:19Z

src/database/config/config.js

@@ -0,0 +1,28 @@
+const dotenv = require('dotenv');
+const pg = require('pg');


'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).

hound · 2024-06-03T10:36:19Z

src/database/config/config.js

@@ -0,0 +1,28 @@
+const dotenv = require('dotenv');


'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).

hound · 2024-06-03T10:36:19Z

src/database/config/config.js

+    dialectModule: pg,
+  },
+  production: {
+    url: `postgres://${process.env.PRO_DB_USER}:${process.env.PRO_DB_PASS}@${process.env.PRO_DB_HOST}/${process.env.PRO_DB_NAME}`,


'template literal syntax' is only available in ES6 (use 'esversion: 6').

hound · 2024-06-03T10:36:19Z

src/database/config/config.js

+    },
+  },
+  test: {
+    url: `postgres://${process.env.TEST_DB_USER}:${process.env.TEST_DB_PASS}@${process.env.TEST_DB_HOST}/${process.env.TEST_DB_NAME}`,


'template literal syntax' is only available in ES6 (use 'esversion: 6').

hound · 2024-06-03T10:36:19Z

src/database/config/config.js

+
+module.exports = {
+  development: {
+    url: `${process.env.DB_URL}`,


'template literal syntax' is only available in ES6 (use 'esversion: 6').

hound · 2024-06-03T10:36:19Z

src/database/config/config.js

@@ -0,0 +1,28 @@
+const dotenv = require('dotenv');
+const pg = require('pg');


'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).

hound · 2024-06-03T10:36:19Z

src/database/config/config.js

@@ -0,0 +1,28 @@
+const dotenv = require('dotenv');


'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).

hound · 2024-06-03T10:36:20Z

src/database/migrations/20240512215421-create-users.js

+        type: Sequelize.DATE,
+        allowNull: true
+      }
+    });


Unrecoverable syntax error. (90% scanned).

hound · 2024-06-03T10:36:20Z

src/database/migrations/20240512215421-create-users.js

+/** @type {import('sequelize-cli').Migration} */
+module.exports = {
+  async up(queryInterface, Sequelize) {
+    await queryInterface.createTable('users', {


Expected an assignment or function call and instead saw an expression.
Missing semicolon.

hound · 2024-06-03T10:36:20Z

src/database/migrations/20240512215421-create-users.js

@@ -0,0 +1,69 @@
+/** @type {import('sequelize-cli').Migration} */
+module.exports = {
+  async up(queryInterface, Sequelize) {


Expected ':' and instead saw 'up'.
Expected '}' to match '{' from line 2 and instead saw '{'.
Missing semicolon.

hound · 2024-06-03T10:36:20Z

src/database/config/config.js

+    dialectModule: pg,
+  },
+  production: {
+    url: `postgres://${process.env.PRO_DB_USER}:${process.env.PRO_DB_PASS}@${process.env.PRO_DB_HOST}/${process.env.PRO_DB_NAME}`,


'template literal syntax' is only available in ES6 (use 'esversion: 6').

hound · 2024-06-03T10:36:20Z

src/database/config/config.js

+    },
+  },
+  test: {
+    url: `postgres://${process.env.TEST_DB_USER}:${process.env.TEST_DB_PASS}@${process.env.TEST_DB_HOST}/${process.env.TEST_DB_NAME}`,


'template literal syntax' is only available in ES6 (use 'esversion: 6').

hound · 2024-06-03T10:36:20Z

src/database/config/config.js

+
+module.exports = {
+  development: {
+    url: `${process.env.DB_URL}`,


'template literal syntax' is only available in ES6 (use 'esversion: 6').

hound · 2024-06-03T10:36:20Z

src/database/config/config.js

@@ -0,0 +1,28 @@
+const dotenv = require('dotenv');
+const pg = require('pg');


'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).

hound · 2024-06-03T10:36:20Z

src/database/config/config.js

@@ -0,0 +1,28 @@
+const dotenv = require('dotenv');


'const' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).

hound · 2024-06-03T10:36:20Z

src/database/models/index.js

+    file.indexOf('.') !== 0
+      && file !== basename
+      && file.slice(-3) === '.js'
+      && file.indexOf('.test.js') === -1


Misleading line break before '&&'; readers may interpret this as an expression boundary.

hound · 2024-06-03T10:36:21Z

src/database/models/index.js

+  .filter((file) => (
+    file.indexOf('.') !== 0
+      && file !== basename
+      && file.slice(-3) === '.js'


Misleading line break before '&&'; readers may interpret this as an expression boundary.

hound · 2024-06-03T10:36:21Z

src/database/models/index.js

+  .readdirSync(__dirname)
+  .filter((file) => (
+    file.indexOf('.') !== 0
+      && file !== basename


Misleading line break before '&&'; readers may interpret this as an expression boundary.

hound · 2024-06-03T10:36:21Z

src/database/models/index.js

+
+fs
+  .readdirSync(__dirname)
+  .filter((file) => (


'arrow function syntax (=>)' is only available in ES6 (use 'esversion: 6').

hound · 2024-06-03T10:36:21Z

src/database/models/index.js

+const config = require(`${__dirname}/../config/config.json`)[env];
+const db = {};
+
+let sequelize;


'let' is available in ES6 (use 'esversion: 6') or Mozilla JS extensions (use moz).

Merge pull request #1 from atlp-rwanda/ft-express-setup

883aa63

Initial commit: Set up empty Node.js Express application structure an…

kennyg37 requested review from SHYAKA-Aime, mutsinziisaac, GabrielDushime, jamesndekezi and mugishaj092 May 24, 2024 13:22

kennyg37 force-pushed the ft-verification-email-validation branch from 505b798 to 54da5ca Compare May 24, 2024 13:35

hound bot reviewed May 24, 2024

View reviewed changes

mugishaj092 requested changes May 27, 2024

View reviewed changes

GabrielDushime approved these changes May 27, 2024

View reviewed changes

mutsinziisaac previously approved these changes May 27, 2024

View reviewed changes

hound bot reviewed May 27, 2024

View reviewed changes

GabrielDushime previously approved these changes May 27, 2024

View reviewed changes

hound bot reviewed May 27, 2024

View reviewed changes

kennyg37 requested a review from mugishaj092 May 28, 2024 07:46

hound bot reviewed May 28, 2024

View reviewed changes

mugishaj092 previously approved these changes May 28, 2024

View reviewed changes

hound bot reviewed May 28, 2024

View reviewed changes

hound bot reviewed May 30, 2024

View reviewed changes

kennyg37 force-pushed the ft-verification-email-validation branch 18 times, most recently from cc8a7e0 to caa2bd5 Compare June 3, 2024 10:33

solving conflicts

558ecd0

kennyg37 force-pushed the ft-verification-email-validation branch from caa2bd5 to 558ecd0 Compare June 3, 2024 10:36

hound bot reviewed Jun 3, 2024

View reviewed changes

kennyg37 closed this Jun 3, 2024

kennyg37 removed the Changes requested label Jun 3, 2024

kennyg37 deleted the ft-verification-email-validation branch June 3, 2024 10:50

		@@ -0,0 +1,28 @@
		const dotenv = require('dotenv');
		const pg = require('pg');

Ft verification email validation #23

Ft verification email validation #23

Conversation

kennyg37 commented May 24, 2024

What does this PR do?

Describe your changes

PR Type

How should this be manually tested?

What are the relevant pivotal tracker stories?

Screenshots (if is appropriate)

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

mugishaj092 left a comment • edited Loading

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

GabrielDushime left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

gitguardian bot commented May 27, 2024 • edited Loading

️✅ There are no secrets present in this pull request anymore.

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

hound bot left a comment

Choose a reason for hiding this comment

hound bot Jun 3, 2024

Choose a reason for hiding this comment

hound bot Jun 3, 2024

Choose a reason for hiding this comment

hound bot Jun 3, 2024

Choose a reason for hiding this comment

hound bot Jun 3, 2024

Choose a reason for hiding this comment

hound bot Jun 3, 2024

Choose a reason for hiding this comment

hound bot Jun 3, 2024

Choose a reason for hiding this comment

hound bot Jun 3, 2024

Choose a reason for hiding this comment

hound bot Jun 3, 2024

Choose a reason for hiding this comment

hound bot Jun 3, 2024

Choose a reason for hiding this comment

hound bot Jun 3, 2024

Choose a reason for hiding this comment

hound bot Jun 3, 2024

Choose a reason for hiding this comment

hound bot Jun 3, 2024

Choose a reason for hiding this comment

mugishaj092 left a comment •

edited

Loading

gitguardian bot commented May 27, 2024 •

edited

Loading