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

Jump to bottom

Add a section to heir.dev explaining the merge procedure #546

Closed

j2kun opened this issue Mar 23, 2024 · 1 comment · Fixed by #552

Assignees

Collaborator

j2kun commented Mar 23, 2024

Also: what we get for having to put up with it.

j2kun self-assigned this

Collaborator

asraa commented Mar 23, 2024

I wrote some pre-existing "PR flow here" but it would greatly benefit from a flowchart and the rationale (and maybe mention of what copybara is)
https://heir.dev/docs/contributing/#pull-request-review-flow

j2kun mentioned this issue

[docs] Add section about copybara workflow #552

Merged

copybara-service bot closed this as completed in #552

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