You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having had no end of trouble releasing v1.18 of XModAlg, this document has been a great help.
(1) The release process (extended version) 7.
I found that I had to include --token ...... here.
(2) The release process (extended version) 9.
My problem with 'git push' was that, with XModAlg, my master points to cdwensley/xmodalg while upstream points to gap-packages/xmodalg. Eventually discovered that 'git push -f upstream' appeared to work. So maybe a comment here that a remote may need to be added to 'git push'?
The text was updated successfully, but these errors were encountered:
@cdwensley I am really sorry that you (once again) had such big trouble :-(. Did the emails by @alex-konovalov and me help any?
Regarding (1): well, that is one way to deal with the token; there are others, as described in section "GitHub access token". So I am loath to mention --token specifically (e.g. I never use that, for security reasons, as it means my access token ends up in the bash history file). However, perhaps it'd help if at the start of that section there was a reminder that all steps below require an access token to be set up?
Also, perhaps the very first thing the script should do is to probe for the token and then also test it (by doing something that uses the token to read something or so).
Regarding (2): I agree that there should be more of an explanation. Also, PR #71 is related.
Yes - as always you and Alex are a great help.
The problems I encountered were mostly of my own making.
There's usually such a long period of time between making releases that I forget a lot of what happens - despite taking careful printouts from time to time.
The section "GitHub access token" has appeared too formidable in the past, but I have worked through it today and will find out how successful that has been when I next release XMod.
Having had no end of trouble releasing v1.18 of XModAlg, this document has been a great help.
(1) The release process (extended version) 7.
I found that I had to include --token ...... here.
(2) The release process (extended version) 9.
My problem with 'git push' was that, with XModAlg, my master points to cdwensley/xmodalg while upstream points to gap-packages/xmodalg. Eventually discovered that 'git push -f upstream' appeared to work. So maybe a comment here that a remote may need to be added to 'git push'?
The text was updated successfully, but these errors were encountered: