Skip to content

Update GitHub strategy to include agentic PR's #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
d33bs merged 3 commits into from
Feb 6, 2026
Merged

Update GitHub strategy to include agentic PR's #22

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c7f0adb
update github strategy to include agentic prs
d33bs Feb 6, 2026
20ea939
update software examples
d33bs Feb 6, 2026
e03f77c
Update github_strategy.md
d33bs Feb 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion github_strategy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ We follow standard procedures when writing software packages including:

- Gallery outlining example use cases

Examples: [pycytominer](https://github.com/cytomining/pycytominer), [CytoSnake](https://github.com/WayScience/CytoSnake)
Examples: [pycytominer](https://github.com/cytomining/pycytominer), [coSMicQC](https://github.com/cytomining/coSMicQC)

### 2. Analysis repository

Expand Down Expand Up @@ -135,6 +135,8 @@ This process has many direct and indirect benefits.

- The smaller the better; it is WAY easier to review if small

1. **Agentic PRs:** If a pull request is created by a non-human actor (e.g., an agent or LLM model), treat it as a human-authored PR for review purposes. The person who initiated the agent action is considered the author (alongside the agent) and the PR still benefits from outside review by others. One outside approval is still required for merging.

1. The writer adds details to the pull request in markdown format

- Justifies the rationale for why the pull request exists
Expand Down