-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exiv2_v0.27.5RC3 #1938
exiv2_v0.27.5RC3 #1938
Conversation
I must have missed one of the conan invocations. |
Codecov Report
@@ Coverage Diff @@
## 0.27-maintenance #1938 +/- ##
=================================================
Coverage 46.32% 46.32%
=================================================
Files 146 146
Lines 22950 22950
Branches 11781 11781
=================================================
Hits 10632 10632
Misses 6702 6702
Partials 5616 5616 Continue to review full report at Codecov.
|
Bollocks. git refuses my fix: 0.27-maintenance -> 0.27-maintenance (refusing to allow an OAuth App to create or update workflow I think the change is here in .github/workflows/on_PR_windows_matrix.yml
|
Hang on. I was looking at this from my phone before, but I am at my desk now. I'll see if I can fix it. |
aeffd85
to
3edca8c
Compare
It looks like it wasn't running with the latest version of the CI, so I have tried rebasing the commits onto the latest 0.27-maintenance. |
Thanks @kevinbackhouse For me, git is mostly a mystery. I know about 6 commands and that's it. |
@clanmills: that's me with cmake! It seems like a bunch of magic incantations that I have very little interest in learning. |
Luis's the cmake man. He actually likes it! I confess to liking Windows. |
Well done, @kevinbackhouse. Now I have to figure out how to remove two dead commits from my branch. Probably easier to pull down a fresh copy from GitHub. I believe that's the fix for about 90% of git troubles. |
Do you mean you want to squash this into a single commit? I think you might be able to do that from the dropdown on the "merge" button. |
@clanmills: I just had another look at this. Do you just want to get rid of the two "build trigger" commits? I can do that if you like. Or you can do it like this: git checkout exiv2_v0.27.5RC3
git reset --hard exiv2_v0.27.5RC3~2
git push --force |
I got rid of the build triggers using the SmartGit GUI. That was straightforward. I deleted the local branch and pulled a mint copy from GitHub. Rather scared of a command such as Less nervous about |
@clanmills: The easiest solution is to push another commit to edit the files to how you want them, then use the "squash and merge" option: |
I heard Dan talking about squashing. I thought squash was something to drink on a hot summer's day! Ah, yes. That makes sense. More questions:
I'm going to merge this PR, tag 0.27-maintenance and publish the RC3 on GitHub. You've done a great job on v0.27.5. This is "Kev's Release". |
The answer to 1 is that I did a rebase. I.e. I took your 3 commits and reapplied them to the latest version of 0.27-maintenance. The sequence of commands was something like this: git checkout exiv2_v0.27.5RC3
git rebase origin/0.27-maintenance
git push --force To be honest, I have never heard of I often use the |
Ah!! Right. Now I know what rebase is. Thanks for the explanation. |
No description provided.