Skip to content

Comments

[5.1] upmerges 2023-10-16#42145

Closed
LadySolveig wants to merge 1 commit intojoomla:5.1-devfrom
LadySolveig:5.1/upmerges/2023-10-16
Closed

[5.1] upmerges 2023-10-16#42145
LadySolveig wants to merge 1 commit intojoomla:5.1-devfrom
LadySolveig:5.1/upmerges/2023-10-16

Conversation

@LadySolveig
Copy link
Contributor

Pull Request for Issue # .

Summary of Changes

Testing Instructions

Actual result BEFORE applying this Pull Request

Expected result AFTER applying this Pull Request

Link to documentations

Please select:

  • Documentation link for docs.joomla.org:

  • No documentation changes for docs.joomla.org needed

  • Pull Request link for manual.joomla.org:

  • No documentation changes for manual.joomla.org needed

@joomla-cms-bot joomla-cms-bot added Language Change This is for Translators NPM Resource Changed This Pull Request can't be tested by Patchtester PR-5.1-dev labels Oct 16, 2023
@LadySolveig LadySolveig enabled auto-merge October 16, 2023 18:37
@LadySolveig LadySolveig disabled auto-merge October 16, 2023 18:40
@LadySolveig LadySolveig enabled auto-merge October 16, 2023 18:43
@LadySolveig LadySolveig changed the title Merge remote-tracking branch 'joomla/5.0-dev' into 5.1/upmerges/2023-10-16 [5.1] upmerges 2023-10-16 Oct 16, 2023
@richard67
Copy link
Member

@LadySolveig You should not use s quash commit but a merge commit, otherwise the change history for the single commits from 5.0-dev will get lost. The GitHub UI is a bit tricky. The green button remembers what you have used last time, squash or merge, so if you come from daily maintainer work with merging PRs, which is done with squash, and then want to merge up branches, which has to be done with merge, you have to toggle the commit type with the dropdown of the green merge button before merging.

@richard67
Copy link
Member

P.S.: I also can't see the changes from this PR in the changes here, so the upmerge here is either outdated or there is something else wrong: #42103 .

@LadySolveig
Copy link
Contributor Author

@LadySolveig You should not use s quash commit but a merge commit, otherwise the change history for the single commits from 5.0-dev will get lost. The GitHub UI is a bit tricky. The green button remembers what you have used last time, squash or merge, so if you come from daily maintainer work with merging PRs, which is done with squash, and then want to merge up branches, which has to be done with merge, you have to toggle the commit type with the dropdown of the green merge button before merging.

Absolutly right, sorry I forgot to change after editing the title.

@richard67
Copy link
Member

No need for sorry. That green button is really a tricky thing.

@LadySolveig LadySolveig deleted the 5.1/upmerges/2023-10-16 branch October 16, 2023 20:14
@LadySolveig
Copy link
Contributor Author

LadySolveig commented Oct 16, 2023

P.S.: I also can't see the changes from this PR in the changes here, so the upmerge here is either outdated or there is something else wrong: #42103 .

#42146
I don't know what I've done - now the PR is there. Thank you!

@richard67
Copy link
Member

#42146 looks good, all right.

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

Labels

Language Change This is for Translators NPM Resource Changed This Pull Request can't be tested by Patchtester

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants