kylemanna / kylemanna/systemd-utils
Consider using RESULT / JOB_RESULT instead of parsing message
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 89
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
I imagine this change (broadens) the scope of what emails get sent, so you might not like it as a breaking change. I am probably going to this anyway with a fork for me, but if you'd like the change pulled in I'll contribute once I have tested it. If not feel free to close.
Contributor guide
No contributing guide indexed for this repository
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 source file or test is named in the issue. Start by locating the current message-parsing path and reviewing how RESULT or JOB_RESULT is handled; the issue does not define tests or clear acceptance criteria for when the broader email scope is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100