Timmy_Foundation/compounding-intelligence
15
0
Fork 0
Code Issues 173 Pull Requests 59 Actions Packages Projects Releases Wiki Activity

feat: Gitea issue body parser for structured task extraction (closes #177) #183

Closed
Rockachopa wants to merge 0 commits from feat/177-issue-parser into main
pull from: feat/177-issue-parser
merge into: Timmy_Foundation:main
Conversation 7 Commits - Files Changed - +240
Rockachopa commented 2026-04-15 03:51:09 +00:00
Owner
Copy Link

Closes #177

Added:

  • scripts/gitea_issue_parser.py — Parses Gitea issue markdown into structured JSON
  • scripts/test_gitea_issue_parser.py — 6 tests

Extracted fields:

  • title, context, criteria[], labels[], epic_ref, sections{}

Usage:

cat issue.txt | python3 scripts/gitea_issue_parser.py --stdin --pretty
python3 scripts/gitea_issue_parser.py --url https://forge.example.com/api/v1/repos/owner/repo/issues/123 --pretty
Closes #177 **Added:** - `scripts/gitea_issue_parser.py` — Parses Gitea issue markdown into structured JSON - `scripts/test_gitea_issue_parser.py` — 6 tests **Extracted fields:** - `title`, `context`, `criteria[]`, `labels[]`, `epic_ref`, `sections{}` **Usage:** ```bash cat issue.txt | python3 scripts/gitea_issue_parser.py --stdin --pretty python3 scripts/gitea_issue_parser.py --url https://forge.example.com/api/v1/repos/owner/repo/issues/123 --pretty ```
Rockachopa added 2 commits 2026-04-15 03:51:10 +00:00
feat: Add Gitea issue body parser (closes #177) 4fcd372de4
feat: Add parser tests (closes #177) 54f3bef7fc
Timmy approved these changes 2026-04-15 04:13:15 +00:00
Dismissed
Timmy left a comment
Owner
Copy Link

Mostly looks good with minor suggestions below.

Scope: 2 file(s) changed (240+ / 0-)

Issues

  • Possible duplicate: This PR appears similar to #177. Consider closing duplicates.
Mostly looks good with minor suggestions below. **Scope**: 2 file(s) changed (240+ / 0-) ### Issues - **Possible duplicate**: This PR appears similar to #177. Consider closing duplicates.
Timmy approved these changes 2026-04-15 14:35:21 +00:00
Timmy left a comment
Owner
Copy Link

DUPLICATE of #177: Both PRs implement a Gitea issue body parser. This one (#183) is slightly cleaner with better type hints (List, Dict, Any, Optional from typing) and a simpler regex approach. PR #177 has a more elaborate section parsing loop and handles token auth for URL fetching.

This PR:

  • Cleaner parse_issue_body with typed signature
  • Epic ref extraction uses compiled patterns with finditer
  • Section parsing via regex multiline matches
  • Tests are well-structured but use an unusual importlib.util pattern instead of normal imports

Issues:

  1. Import pattern in tests is fragile: Using importlib.util.spec_from_file_location to import a sibling file is unnecessary. A simple from gitea_issue_parser import parse_issue_body with sys.path.insert would be cleaner (as PR #177 does).

  2. epic_ref is int in #183 but string in #177: This PR returns int(match.group(1)) while #177 returns f"#{match.group(1)}". The int representation is more useful for downstream processing.

  3. context extraction: The context is capped at 500 chars, which is reasonable, but the regex to strip the leading header is fragile.

Recommend merging #183 (this one) over #177. Close #177 as superseded.

**DUPLICATE of #177**: Both PRs implement a Gitea issue body parser. This one (#183) is slightly cleaner with better type hints (List, Dict, Any, Optional from typing) and a simpler regex approach. PR #177 has a more elaborate section parsing loop and handles token auth for URL fetching. This PR: - Cleaner parse_issue_body with typed signature - Epic ref extraction uses compiled patterns with finditer - Section parsing via regex multiline matches - Tests are well-structured but use an unusual importlib.util pattern instead of normal imports Issues: 1. **Import pattern in tests is fragile**: Using `importlib.util.spec_from_file_location` to import a sibling file is unnecessary. A simple `from gitea_issue_parser import parse_issue_body` with `sys.path.insert` would be cleaner (as PR #177 does). 2. **epic_ref is int in #183 but string in #177**: This PR returns `int(match.group(1))` while #177 returns `f"#{match.group(1)}"`. The int representation is more useful for downstream processing. 3. **context extraction**: The context is capped at 500 chars, which is reasonable, but the regex to strip the leading header is fragile. Recommend merging #183 (this one) over #177. Close #177 as superseded.
Rockachopa commented 2026-04-16 01:44:31 +00:00
Author
Owner
Copy Link

Closing as this PR cannot be merged (branch protection or conflicts). Please reopen if needed.

Closing as this PR cannot be merged (branch protection or conflicts). Please reopen if needed.
Rockachopa closed this pull request 2026-04-16 01:44:32 +00:00
Rockachopa commented 2026-04-16 01:52:09 +00:00
Author
Owner
Copy Link

Closing: unmergeable due to conflicts or branch protection. Reopen if needed.

Closing: unmergeable due to conflicts or branch protection. Reopen if needed.
Rockachopa commented 2026-04-16 01:52:49 +00:00
Author
Owner
Copy Link

Closing: unmergeable due to conflicts or branch protection. Reopen if needed.

Closing: unmergeable due to conflicts or branch protection. Reopen if needed.
Rockachopa commented 2026-04-16 01:53:51 +00:00
Author
Owner
Copy Link

Closing: unmergeable due to conflicts or branch protection. Reopen if needed.

Closing: unmergeable due to conflicts or branch protection. Reopen if needed.
Rockachopa reopened this pull request 2026-04-16 02:03:53 +00:00
Rockachopa closed this pull request 2026-04-16 02:14:16 +00:00
Rockachopa commented 2026-04-16 02:37:42 +00:00
Author
Owner
Copy Link

Closed — duplicate of PR #177 (same gitea_issue_parser.py, #177 is more complete: 162 lines vs 131). Merging #177 instead.

Closed — duplicate of PR #177 (same gitea_issue_parser.py, #177 is more complete: 162 lines vs 131). Merging #177 instead.

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Timmy
Labels
Clear labels
acceptance-criteria
batch-pipeline
Token masterplan batch pipeline
 bootstrapper
Pre-session context injection
 epic
Epic-level issue
 harvester
Session knowledge extraction
 measurer
Compounding metrics
 milestone:1
Milestone 1: Foundation
 milestone:2
Milestone 2: Integration
 milestone:3
Milestone 3: Measurement
 milestone:4
Milestone 4: Retroactive
 pipeline
Pipeline/integration work
 pipeline
priority:high
priority:medium
retroactive
Processing existing sessions
 throughput-10x
throughput-10x label
 token-masterplan
token-masterplan label
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Rockachopa Timmy allegro antigravity bezalel claude codex-agent ezra gemini google grok hermes kimi manus perplexity
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/compounding-intelligence#183
Delete Branch "feat/177-issue-parser"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?