- Mailing Lists
- Contributors
- Re: Sorry, i'm not familiar with git
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
Re: Sorry, i'm not familiar with git
Hi Martin I made a small research and I'd like to make a try but at the same time I always doubt about the action I'm planning to do on git.
For example in this case I have read in this article https://www.educative.io/answers/how-to-change-a-git-commit-message-after-a-push that I could use:
git commit --amend -m "New message"
git push --force-with-lease repository-name branch-name
but I am not sure about the 'force' or --force-with-lease which seems a less intrusive option. What I don't understand is, if --force 'which will destroy any changes someone else has pushed to the branch' as I read in the article, and --force-with-lease will "abort if there was an upstream change to the repository", is for me enough to fetch the origin before the amend/push to make a safe amend (I am not even sure this sentence makes sense eheh) or maybe it is an alternative way that I don't know?
Thanks,
Francesco
Il giorno gio 19 gen 2023 alle ore 09:27 Francesco Ballerini <francescobl.lavoro@gmail.com> ha scritto:
Thanks, I would appreciate that a lot, if it's easy to solve for you. I was a little bit tired yesterday and don't wanna make even more trouble eheh ... : )Thank you,FrancescoIl giorno gio 19 gen 2023 alle ore 08:32 Martin Trigaux (mat) <notifications@odoo-community.org> ha scritto:On 19/01/2023 00:57, Francesco Ballerini wrote:
Invalid title for commit: ' [FIX] product: add explicit copy arg to property_product_pricelist'
Hello,
This one is because you have a space in the beginning of the commit message, " [FIX]" instead of "[FIX]" ;-)
But don't worry about it if you are not sure how to amend your commit, we can handle it for you if needed.
Martin
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Francesco Ballerini - 06:56 - 19 Jan 2023
Reference
-
Sorry, i'm not familiar with git
Hi everyone, I am discovering git/github/Pull Requests and I am receiving this error.Basically I wanted to ask how can I fix this, but most importantly I want to excuse because I think that I forced pushed while trying to fix it.Not sure if force pushing can really cause problems in protected branches, but I have read it's a really bad practice.I suddenly panicked like I never did, of course, and immediately cancelled PR and made it new. But the error is still here. Not sure about the error, what could I do in this situation?
Invalid title for commit: ' [FIX] product: add explicit copy arg to property_product_pricelist'Thanks in advance,Francesco Ballerini
by Francesco Ballerini - 12:56 - 19 Jan 2023