Repository navigation
Update claims-system.md - #427
Conversation
Update the collaboration claim rule to mark as free. Clean up the own revision claim point
 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| - If a developer makes a revision or subset claim, the claim can be set to "Own Revision" depending on criteria I haven't copy-pasted into this section yet. | ||
| - Collaboration claims. | ||
| - Collaboration claims after the developer's part has been completed. To request a free claim on a completed collaboration claim, the lead of the collaboration sends a message to DevCompliance when they agree that the work of one of the collaborators is ready for release. This includes having serviceable badges. | ||
| - Own revision claims upon request, including subset claims where the developer is the author or claimant of the base set. |
There was a problem hiding this comment.
This grants free subset claims to non-author base-set claimants, while subset_design.md says developers without core-set authorship are ineligible. The conflicting rules can cause claims to be marked free incorrectly.
There was a problem hiding this comment.
This was already how things worked out for concurrent claims. The subset page just does not mention that practice, it's not in explicit contradiction.
There was a problem hiding this comment.
That’s fair. If the subset guidance does not explicitly prohibit this and the free-claim treatment reflects the established practice for concurrent claims, then this is not a documentation conflict. I’m withdrawing the finding.
Tip: You can customize Greptile's behavior for this repo with .greptile/rules.md and .greptile/config.json.
2 participants
Update the collaboration claim rule to mark as free. Clean up the own revision claim point