Skip to content

tidy: Add AI policy to contributing#925

Open
KSkwarczynski wants to merge 3 commits into
developfrom
kskwarczynski/tidy/aipolicy
Open

tidy: Add AI policy to contributing#925
KSkwarczynski wants to merge 3 commits into
developfrom
kskwarczynski/tidy/aipolicy

Conversation

@KSkwarczynski
Copy link
Copy Markdown
Member

@KSkwarczynski KSkwarczynski commented Jun 5, 2026

Pull request description

I know Dan, Ewan and Henry agrees with the concept of AI policy.

I would appreciate any comment to the actual content of the policy.

Most of this is obvious, but useful to write openly

@KSkwarczynski KSkwarczynski self-assigned this Jun 5, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 5, 2026

Hi @KSkwarczynski, thank you for contributing to MaCh3! Please wait for MaCh3 developers to review your PR. If no one answers within a week, please message people from this list: https://github.com/orgs/mach3-software/teams/mach3admin . While waiting, please enjoy this

meme

Use this action on your projects. Use jokes on issues instead.

@github-actions github-actions Bot added the CI/CD 🤖 CI/CD label Jun 5, 2026
KSkwarczynski
KSkwarczynski commented Jun 5, 2026
View reviewed changes
Copy link
Copy Markdown
Member Author

@KSkwarczynski KSkwarczynski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.80.

Benchmark suite Current: 6be43e6 Previous: d491feb Ratio
Beam Reweight w/o Osc 4.74246 ms (± 4.90509) 2.44262 ms (± 187.379) 1.94

This comment was automatically generated by workflow using github-action-benchmark.

henry-wallace-phys
henry-wallace-phys reviewed Jun 5, 2026
View reviewed changes
Comment thread .github/CONTRIBUTING.md Outdated
The following rules are in service of producing correct, maintainable code while not inundating the maintainers.

1. You (the author of the PR) are responsible for the PR, regardless of the tools you use to create it. Make sure you understand it thoroughly and agree with its contents before you submit a PR.
2. Corollary: AI is not a co-author, AI is a tool. If you wouldn't list Emacs as a co-author, don't list Claude either.
Copy link
Copy Markdown
Contributor

@henry-wallace-phys henry-wallace-phys Jun 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we make this clearer i.e. "we will not allow AI to directly commit to MaCh3" [assuming there is a quorum on that]

Copy link
Copy Markdown
Member Author

@KSkwarczynski KSkwarczynski Jun 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am in strong, yes. It might be easier if you just modify PR accordingly and we merge later

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 5, 2026

Hi, I am MaCh3-Telemetry bot

Memory and CPU Usage Summary

### Memory and CPU Usage Summary

| Metric  |     Mean    |      Max    |
|---------|-------------|-------------|
| **RAM** |   357.33 MB |   359.49 MB |
| **CPU** |    96.60 %  |    98.00 %  |

Memory Usage Plot

You can view the memory usage plot directly in the job summary from the link above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@henry-wallace-phys henry-wallace-phys henry-wallace-phys left review comments

At least 1 approving review is required to merge this pull request.

Assignees

@KSkwarczynski KSkwarczynski

Labels

CI/CD 🤖 CI/CD

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@KSkwarczynski @henry-wallace-phys