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

[Merged by Bors] - chore(PULL_REQUEST_TEMPLATE.md): add template for moves and deletions #14559

Closed
wants to merge 4 commits into from

Conversation

jcommelin
Copy link
Member


Open in Gitpod

Copy link

github-actions bot commented Jul 9, 2024

PR summary 3d0ea229c3

Import changes for modified files

No significant changes to the import graph

Import changes for all files
Files Import difference

Declarations diff

No declarations were harmed in the making of this PR! 🐙

You can run this locally as follows
## summary with just the declaration names:
./scripts/no_lost_declarations.sh short <optional_commit>

## more verbose report:
./scripts/no_lost_declarations.sh <optional_commit>

@semorrison
Copy link
Contributor

Is the intention that a bot will fill this in?

@jcommelin
Copy link
Member Author

Maybe not directly filling in, but certainly the intention is that a bot will generate a first draft that can be copy-pasta-edited.

@adomani
Copy link
Collaborator

adomani commented Jul 9, 2024

In particular, the pairs of declarations that decl_diff matches, are good candidates for Moves and the ones that have an unmatched - are good candidates for Deletions.

@semorrison semorrison added the awaiting-author A reviewer has asked the author a question or requested changes label Jul 9, 2024
Co-authored-by: damiano <adomani@gmail.com>
@jcommelin jcommelin removed the awaiting-author A reviewer has asked the author a question or requested changes label Jul 10, 2024
@adomani
Copy link
Collaborator

adomani commented Jul 10, 2024

I looked briefly into this and I am only seeing hacky ways of getting a PR template that depends on the PR itself.

As far as I understand, GitHub simply reads the file that this PR is editing and uses that as a template. So, this file would have had to be edited between pushing and creating a PR. For instance, the very first action upon pushing could be to compute the decl_diff, modify the PR_template file and then have it ready by the time you actually open the PR!

I wonder if not git-indexing this file and simply regenerating it on every push would give the "personalised touch" that we want.

@semorrison
Copy link
Contributor

I think if we develop a bot that can contribute answers here, it should just run after the PR is open. We can add a note to the template saying "You don't need to fill this in immediately: a bot will edit the PR top comment shortly with a first approximation, and you should check that it looks right."

@semorrison
Copy link
Contributor

bors merge

@github-actions github-actions bot added the ready-to-merge This PR has been sent to bors. label Jul 10, 2024
@mathlib-bors
Copy link
Contributor

mathlib-bors bot commented Jul 10, 2024

Build failed (retrying...):

@mathlib-bors
Copy link
Contributor

mathlib-bors bot commented Jul 10, 2024

Pull request successfully merged into master.

Build succeeded:

@mathlib-bors mathlib-bors bot changed the title chore(PULL_REQUEST_TEMPLATE.md): add template for moves and deletions [Merged by Bors] - chore(PULL_REQUEST_TEMPLATE.md): add template for moves and deletions Jul 10, 2024
@mathlib-bors mathlib-bors bot closed this Jul 10, 2024
@mathlib-bors mathlib-bors bot deleted the jcommelin-patch-1 branch July 10, 2024 18:31
@adomani adomani mentioned this pull request Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge This PR has been sent to bors.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants