git - Labels

List tags, while in repo folder, type command:

git show-ref --tags

echo-private

d8d21935beff3393f488b0cbc5787c20111b789d refs/tags/QA_July2025_A

• Initiated QA process

8f39e0a29b99557d37c3ff95062e2698d071537d refs/tags/QA_July2025_A_Checkpoint1

• 2025-08-03 - Removed secrets issues

a91d2554977234343d37f89dc8fe42935725ce38 refs/tags/QA_July2025_A_Checkpoint2

• 2025-08-03 - Running on new environment, laptop 2. Instructions here, and environmental keys notes here

---

identity-backend

acf59a12cd4616dc175ae84837930b0bbd4771f3 refs/tags/QA_July2025_A_Checkpoint1

• 2025-08-03 - Removed secrets issues

64317f07b348de57e03781f23056388881731fea refs/tags/v1.0.0

f1f98e39af5cae39dc90b9c26cf72a7105cd5b9f refs/tags/QA_July2025_A_Checkpoint2

• 2025-08-03 - Running on new environment, laptop 2. Instructions here, and environmental keys notes here

---

How to?

# In identity-service

git add requirements.txt README.md

git commit -m "Fix JWT library, pin dependencies, update README with setup guide"

# In echo-private

git add requirements.txt README.md

git commit -m "Fix JWT library, pin dependencies, update README with setup guide"

---

---

PS C:\Users\saad0\Documents\source\echo-private> git tag -a QA_July2025_A_Checkpoint1 -m "Checkpoint during August QA cycle on top of QA_July2025_A"

PS C:\Users\saad0\Documents\source\echo-private> git push origin QA_July2025_A_Checkpoint1

Enumerating objects: 1, done.

Counting objects: 100% (1/1), done.

Writing objects: 100% (1/1), 201 bytes | 201.00 KiB/s, done.

Total 1 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)

To https://github.com/saadaziz/echo-private.git

 * [new tag]         QA_July2025_A_Checkpoint1 -> QA_July2025_A_Checkpoint1

PS C:\Users\saad0\Documents\source\echo-private> cd ..

PS C:\Users\saad0\Documents\source> cd .\identity-backend\

PS C:\Users\saad0\Documents\source\identity-backend> git tag -a QA_July2025_A_Checkpoint1 -m "Checkpoint during August QA cycle on top of QA_July2025_A"

PS C:\Users\saad0\Documents\source\identity-backend> git push origin QA_July2025_A_Checkpoint1

Enumerating objects: 1, done.

Counting objects: 100% (1/1), done.

Writing objects: 100% (1/1), 201 bytes | 201.00 KiB/s, done.

Total 1 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)

To https://github.com/saadaziz/identity-backend.git

 * [new tag]         QA_July2025_A_Checkpoint1 -> QA_July2025_A_Checkpoint1

PS C:\Users\saad0\Documents\source\identity-backend> git fetch --tags

PS C:\Users\saad0\Documents\source\identity-backend> git tag -l | findstr QA_July2025

QA_July2025_A_Checkpoint1

PS C:\Users\saad0\Documents\source\identity-backend> cd ..

PS C:\Users\saad0\Documents\source> cd .\echo-private\

PS C:\Users\saad0\Documents\source\echo-private> git fetch --tags

PS C:\Users\saad0\Documents\source\echo-private> git tag -l | findstr QA_July2025

QA_July2025_A

QA_July2025_A_Checkpoint1

PS C:\Users\saad0\Documents\source\echo-private>

Here’s how to create and document your new checkpoint tag on top of QA_July2025_A for both repos, and make sure you can restore them quickly during QA.

---

1. Confirm Current State

Make sure both repos are clean (no uncommitted changes):

cd path/to/echo-private
git status
cd path/to/identity-backend
git status

If there are staged changes you want included, commit them first. If not, stash or discard them.

---

2. Fetch Existing Tags

Ensure QA_July2025_A exists locally and is up-to-date:

git fetch --tags
git tag -l | grep QA_July2025_A

If missing locally:

git checkout QA_July2025_A

Then return to your working branch (likely main):

git checkout main
git merge QA_July2025_A   # optional: bring in previous QA state

---

3. Create New Tag (Checkpoint)

Decide on new tag name, e.g.:

QA_July2025_A_Checkpoint1

Create annotated tag (preferred for QA history):

git tag -a QA_July2025_A_Checkpoint1 -m "QA checkpoint during August QA cycle on top of QA_July2025_A"
git push origin QA_July2025_A_Checkpoint1

Repeat for second repo.

---

4. Quick Restore in Future

To restore later:

git fetch --tags
git checkout QA_July2025_A_Checkpoint1

or to create a branch from tag:

git checkout -b qa_restore QA_July2025_A_Checkpoint1

---

5. Document the QA Tag

Example document for your QA report:

---

QA Report for Tag QA_July2025_A_Checkpoint1

• Tag/Commit: QA_July2025_A_Checkpoint1 (abc1234)

• Date: 2025-08-03

• QA Outcomes: Baseline checkpoint created during mid-cycle; passes all regression tests except noted below.

• Environment: Windows 10, Python 3.12, requirements.txt as of tag

• Notes: Use this tag to restore mid-cycle state if future QA tests break.

---

Issue Found

• Step: Upload new2.txt and query with model=Ollama

• Bug: Query misses "Amira" item

• Log excerpt:

[2025-08-03 12:15:02] Parser INFO: Parsed 321 chars from doc.
[2025-08-03 12:15:04] Query WARN: Missing expected item 'Amira'

• Screenshot: (insert)

---

Repro Instructions

1. Stop all services.

2. Delete logs.db, jobs.db.

3. Clear doc_store/.

4. Start services in order: logging → parser → api_gateway → worker.

5. Upload new1.txt, then new2.txt.

6. Run query:
   "summarize all todo items (due date, title, description)".

---

Known MVP Security Shortcuts

• Hardcoded dev credentials

• verify_signature=False in JWT decode

• Public /logs endpoint

• No CSRF on forms

To fix before prod:

• Move credentials to .env

• Verify JWT signatures

• Secure logs behind auth

• Add CSRF protection for POST forms

---

Links

• CPanel Multi-Microservice Limitations

• Worker.py Bug Report

---

Do you want me to:

1. Generate the exact tag commands for both repos with your URLs included (copy-paste ready)?

2. Draft full markdown QA report file (QA_July2025_A_Checkpoint1.md) with placeholders for you to fill test results?

3. Add restore instructions section (step-by-step to rollback both repos)?

Which ones do you need now? Or all three?

Perfect — both repos are up-to-date and have clean working trees. That’s exactly where you want to be before tagging.

Next step: Create and push your new checkpoint tag on both repos.

---

Step 1: Decide Tag Name

You want this on top of QA_July2025_A, so let’s name it:

QA_July2025_A_Checkpoint1

---

Step 2: Tag and Push for identity-backend

cd C:\Users\saad0\Documents\source\identity-backend
git tag -a QA_July2025_A_Checkpoint1 -m "Checkpoint during August QA cycle on top of QA_July2025_A"
git push origin QA_July2025_A_Checkpoint1

---

Step 3: Tag and Push for echo-private

cd C:\Users\saad0\Documents\source\echo-private
git tag -a QA_July2025_A_Checkpoint1 -m "Checkpoint during August QA cycle on top of QA_July2025_A"
git push origin QA_July2025_A_Checkpoint1

---

Step 4: Verify

Check that both tags exist on GitHub:

git fetch --tags
git tag -l | findstr QA_July2025_A_Checkpoint1

---

Step 5: Confirm Restore Process

To restore in future:

git fetch --tags
git checkout QA_July2025_A_Checkpoint1

Or to create a working branch from it:

git checkout -b qa_restore QA_July2025_A_Checkpoint1

---

Do you want me to generate the QA report markdown file for this new tag now (using the format you shared, ready for you to fill details)? Or walk you through confirming the tag commit hashes first?