Conversation
|
@eric-murray the PR has been adapted to commonalities v0.6-rc1 |
|
@albertoramosmonagas |
I modify it! thank you @eric-murray, can you approve and merge the PR? |
@eric-murray interesting: even after @albertoramosmonagas renamed the file, GitHub is still showing the individual changes. Might be because: the branch is within the upstream repository and the name change was done within GitHub. |
|
@eric-murray can you merge the current PR to create the rc? |
Yes, I've not seen that before. Might be a new feature! More likely, there is a "right" way to rename a file (i.e. just rename it) and a "wrong" way (delete the old file and upload a "new" file with the new name), and github can only show changes when it is done in the right way. |
https://docs.github.com/en/repositories/working-with-files/managing-files/renaming-a-file ... outside of GitHub it is important to be certain that the result is a "git mv ...", not a delete and new file). |
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Following the pre-release of commonalities v0.6-rc1 and the fall25 M3 deadline, commonalities v0.6-rc1 has been adapted to commonalities v0.6-rc1.
Which issue(s) this PR fixes:
Fixes #15
Special notes for reviewers:
N/A
Changelog input
Additional documentation
This section can be blank.