Identifying a tool's previous comments depending on the comment wording is brittle
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Lately I'm thinking that these checks are very brittle (e.g. if we change the message in any way, we have to remember to update the search too)
Originally posted by @marco-c in https://github.com/mozilla/relman-auto-nag/pull/1564#discussion_r932008481
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
The issue names no files, tests, or entry points; begin by locating the checks that identify a tool's previous comments through comment-text searches. Review how those checks are used before deciding on a less brittle identification method, and consider the work done when changing a message no longer requires updating the search logic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100