[Feature Request] - Include more GitHub Actions metadata for each build command
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 210
- Forks
- 36
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
Description
Currently, Macaron misses useful metadata for build commands. Specifically, it doesn't include the job and step where the build command was called in the database.
Proposed Feature
Store more granular metadata from GitHub Actions workflows in the reports and database. This includes the job and step where the build command was called from.
Use Case
This additional metadata is useful for building third-party artifacts from source.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing how GitHub Actions build-command metadata flows into reports and the database, then identify the existing workflow metadata handling. Done means reports and database records retain the originating job and step for each build command, with coverage for the new metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- build-system, ci-cd, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100