Language Change NPM Resource Changed PR-5.1-dev Pending

User tests: Successful: Unsuccessful:

avatar LadySolveig
LadySolveig
16 Oct 2023

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

avatar LadySolveig LadySolveig - open - 16 Oct 2023
avatar LadySolveig LadySolveig - change - 16 Oct 2023
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 16 Oct 2023
Category Repository JavaScript Administration com_media NPM Change Language & Strings Installation Libraries
avatar LadySolveig LadySolveig - change - 16 Oct 2023
Title
Merge remote-tracking branch 'joomla/5.0-dev' into 5.1/upmerges/2023-10-16
[5.1] upmerges 2023-10-16
avatar LadySolveig LadySolveig - edited - 16 Oct 2023
avatar richard67
richard67 - comment - 16 Oct 2023

@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.

avatar richard67
richard67 - comment - 16 Oct 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 .

avatar LadySolveig LadySolveig - change - 16 Oct 2023
Status Pending Closed
Closed_Date 0000-00-00 00:00:00 2023-10-16 19:55:25
Closed_By LadySolveig
Labels Added: Language Change NPM Resource Changed PR-5.1-dev
avatar LadySolveig LadySolveig - close - 16 Oct 2023
avatar LadySolveig
LadySolveig - comment - 16 Oct 2023

@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.

avatar richard67
richard67 - comment - 16 Oct 2023

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

avatar LadySolveig
LadySolveig - comment - 16 Oct 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!

avatar richard67
richard67 - comment - 16 Oct 2023

#42146 looks good, all right.

Add a Comment

Login with GitHub to post a comment