Skip to content

Conversation

@kdeldycke
Copy link
Collaborator

@kdeldycke kdeldycke commented Mar 26, 2025

In order to test the upcoming 8.2.0 release, I'm working on this PR that is trying to reconcile stable branch with the main branch.

Both branches have diverged a lot, and cannot be merged naively. This PR is fixing the conflicting changes which happened in both branches.

This PR particularly:

Relation to other proposals:

Rowlando13 and others added 30 commits August 14, 2023 00:27
Co-authored-by: Andreas Backx <andreas@backx.org>
Co-authored-by: Andreas Backx <andreas@backx.org>
Remove the per-project files so we don't have to keep them in sync.
GitHub's UI links to everything except the contributing guide, so add a
section about that to the readme.
@kdeldycke kdeldycke changed the title Merge stable into main Merge stable into main; Release 8.2.0 Mar 27, 2025
@kdeldycke kdeldycke marked this pull request as ready for review March 27, 2025 14:57
@kdeldycke
Copy link
Collaborator Author

All tests are passing, branches have been merged, this PR is ready for a 8.2.0 release of Click! 🚀

kdeldycke added a commit to kdeldycke/click-extra that referenced this pull request Mar 31, 2025
Rowlando13
Rowlando13 previously approved these changes Apr 1, 2025
Copy link
Collaborator

@Rowlando13 Rowlando13 left a comment

Choose a reason for hiding this comment

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

I reviewed all the docs and requirements file changes.

@Rowlando13 Rowlando13 marked this pull request as draft April 1, 2025 20:11
@Rowlando13 Rowlando13 marked this pull request as ready for review April 1, 2025 20:11
@Rowlando13 Rowlando13 dismissed their stale review April 1, 2025 20:12

Accidental typo.

@Rowlando13
Copy link
Collaborator

@kdeldycke Can you make a PR for this branch against stable to show that it resolves all the conflicts from stable into main, unless there is an easier way to show that.

@Rowlando13
Copy link
Collaborator

Also thanks for this great PR! I wanted to fix the GitHub actions issues last week but did not get around to it.

@kdeldycke
Copy link
Collaborator Author

@kdeldycke Can you make a PR for this branch against stable to show that it resolves all the conflicts from stable into main, unless there is an easier way to show that.

I already had a hard time reconciling the two branches so not sure I can find a clean way. But I'll try.

@kdeldycke
Copy link
Collaborator Author

@kdeldycke Can you make a PR for this branch against stable to show that it resolves all the conflicts from stable into main, unless there is an easier way to show that.

I'm not sure I understand your request, as this PR is already merging with stable in commit 361915bbc3ccbe59a09585ecfd1fc30bb0697272, see:

Screenshot 2025-04-02 at 11 23 41
Screenshot 2025-04-02 at 11 26 25

@Rowlando13
Copy link
Collaborator

This shows what I wanted. Thanks.

@Rowlando13
Copy link
Collaborator

@kdeldycke Can you please fix the conflicts. @davidism Can you give this a review?

@Rowlando13 Rowlando13 linked an issue Apr 16, 2025 that may be closed by this pull request
34 tasks
@kdeldycke
Copy link
Collaborator Author

@kdeldycke Can you please fix the conflicts. @davidism Can you give this a review?

Just fixed the merge conflicts.

Is it possible to wait too long in merging the main/stable branches? Because I don't have a lot of energy these days to reconcile the two code base again. Especially in light of enhancing the documentation with myst from #2886, which will probably overlaps changes in this PR.

@AndreasBackx tried to fix it 6 months ago in #2830 but abandoned. I tried last month but I find it difficult to keep this PR open. Can you please help me reduce the entropy caused by the branch divergence? 😣

@Rowlando13
Copy link
Collaborator

Yes. Absolutely. I was not planning on merging anything until this is merged. I thought that the merge conflict was missed in the original work. Sorry if I created by merging something. I was waiting for a code review since it is so complex, but in light of it possibly not getting done for a long time, I am going to merge it.

@Rowlando13 Rowlando13 merged commit b7c0ab4 into pallets:main Apr 24, 2025
12 checks passed
@kdeldycke
Copy link
Collaborator Author

I just checked the result of that merge and haven't found any issue. main branch is now clean and contain all contributions from stable and other previously merged PRs. Click 8.2.0 is ready to be packaged and released.

@Rowlando13
Copy link
Collaborator

Sweet!

@Rowlando13 Rowlando13 added this to the 8.2.0 milestone Apr 27, 2025
@Rowlando13 Rowlando13 mentioned this pull request Apr 27, 2025
16 tasks
@sebix sebix mentioned this pull request May 6, 2025
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 12, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

v8.2.0: Release Plan

7 participants