Skip to content
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.

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

Add full changelog in batch-mirror Noir PRs #4108

Closed
Savio-Sou opened this issue Jan 17, 2024 · 0 comments · Fixed by #4376
Closed

Add full changelog in batch-mirror Noir PRs #4108

Savio-Sou opened this issue Jan 17, 2024 · 0 comments · Fixed by #4376
Assignees
Labels
A-devops Area: Devops. E.g. CI / build systems

Comments

@Savio-Sou
Copy link
Member

Savio-Sou commented Jan 17, 2024

Problem

Noir changes happening in this repository are currently mirrored in batches to the Noir repository (e.g. noir-lang/noir#4011), where the batching PR adds only its title (e.g. "Sync aztec-packages") but not its sub-PR's (e.g. "implement keccakf1600 in brillig") to Noir's changelog.

This causes unnecessary friction for changelog readers to discover and learn details of the individual changes being batched.

Take v0.23.0's changelog as an example:

Screenshot 2024-01-17 at 11 59 35

Possible solution

The batching PR should add each of its sub-PRs' titles to the Noir changelog, in replacement of its own title.

One possible way would be to:

  1. Collect all sub-PR titles when generating a batching PR
  2. Override release note additions in the batching PR's body with (1)

Additional note

Make sure we use the full link to sub-PRs (e.g. https://github.com/AztecProtocol/aztec-packages/pull/3914) rather than just their numbers (e.g. #3914).

GitHub would automatically link to unrelated PRs with the same number in the Noir repository if it contains just numbers (e.g. https://github.com/noir-lang/noir/pull/3914).

@Savio-Sou Savio-Sou added the A-devops Area: Devops. E.g. CI / build systems label Jan 17, 2024
@github-project-automation github-project-automation bot moved this to Todo in A3 Jan 17, 2024
@ludamad ludamad self-assigned this Jan 23, 2024
ludamad added a commit that referenced this issue Feb 5, 2024
- We just squash when pushing to Noir. We are more reset the state of
the PR so that it is based off the last time we pull with git subrepo
pull noir.
- We can just do git subrepo pull noir whenever now. It will become the
new PR head, and we'll make one squash commit based on it.
- History is lost doing this, but regained with a heuristic that looks
at the last aztec-packages sync PR that occurred. This also resolves
#4108 making sure
release-please has a good changelog.

misc:
- bumps git subrepo version, ended up not being needed, but why not

---------

Co-authored-by: ludamad <[email protected]>
@github-project-automation github-project-automation bot moved this from Todo to Done in A3 Feb 5, 2024
TomAFrench pushed a commit that referenced this issue Feb 7, 2024
- We just squash when pushing to Noir. We are more reset the state of
the PR so that it is based off the last time we pull with git subrepo
pull noir.
- We can just do git subrepo pull noir whenever now. It will become the
new PR head, and we'll make one squash commit based on it.
- History is lost doing this, but regained with a heuristic that looks
at the last aztec-packages sync PR that occurred. This also resolves
#4108 making sure
release-please has a good changelog.

misc:
- bumps git subrepo version, ended up not being needed, but why not

---------

Co-authored-by: ludamad <[email protected]>
michaelelliot pushed a commit to Swoir/noir_rs that referenced this issue Feb 28, 2024
- We just squash when pushing to Noir. We are more reset the state of
the PR so that it is based off the last time we pull with git subrepo
pull noir.
- We can just do git subrepo pull noir whenever now. It will become the
new PR head, and we'll make one squash commit based on it.
- History is lost doing this, but regained with a heuristic that looks
at the last aztec-packages sync PR that occurred. This also resolves
AztecProtocol#4108 making sure
release-please has a good changelog.

misc:
- bumps git subrepo version, ended up not being needed, but why not

---------

Co-authored-by: ludamad <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-devops Area: Devops. E.g. CI / build systems
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants