-
Notifications
You must be signed in to change notification settings - Fork 1
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
ENHANCE: add issue tracker for alternative contact to mailing list #4
base: main
Are you sure you want to change the base?
Conversation
…eave empty file so it doesn't get overridden by Jekyll/minima default.
…erated from /index.md.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While the content of this contribution is okay, your branch contains a lot of commits which should not be there. Please rebase it interactively on main and then force push, so that commits from the conversion to Jekyll are removed from this PR.
I have these hashes from invoking “git reflog”
So if I invoke
, would this help? I've messed up my local main somehow. |
If your local main is messed up the easiest strategy would be to clone a fresh repository and then rebase this branch on main. |
Unfortunately this is even worse than before. Not only your local main is messed up but your remote one is also broken, thanks to the fact that you've submitted #3 from it. This can be fixed as follows: Add the original repo as remote if not done already: After it is done let's fix branch from this PR.
Accept the commit message and finally Hope this helps, and gives you a good lesson to never, ever submit any contributions from the main branch ever again. |
Marking as a draft until excessive commits are removed. |
Speaks for itself, requesting comment.