This is a meta issue summarizing all tasks for the migration to git.

Required:
issue652 script to clean up the mercurial repositories automatically
issue950 script to convert the mercurial repos automatically
issue951 design and decide for a development workflow in git
issue952 update the buildbot to work on the git repository
issue974 Merge the repository for container recipes into the main repository
remove obsolete files: bitbucket-pipelines.yml, misc/uncrustify.py
Protect all branches on main GitHub repo by adding branch protection for branch name "*".

Desired:
issue940 try github test pipelines, which includes:
  issue970 Find a way to run SoPlex during Github actions
  issue971 Find a way to run CPLEX during Github actions
issue953 support git in the repo tool
issue973 Configure the Github repository
issue977 Enforce naming conventions for git repository
issue968 precommit hook to prepend the branch nameto commit messages
issue976 convert .hgignore to .gitignore

Optional:
issue975 move releases to GitHub

The issues actually mentioned in the summary are all closed.

We have a few issues mentioned in the discussion that we don't necessarily see as part of this. Can we mark this one as resolved?

I'll do it tentatively, but of course feel free to reopen.

Added issue977 to summary, which used to be referenced only indirectly from issue973.

Following Silvan's msg10147, I have now removed the Gurobi issue from the summary.

I'm removing Gurobi from this issue and added it to issue926 (support for Gurobi).

Let's discuss the other itmes in the next Fast Downward meeting. We could also include issue1001.

It would be nice to close this.

There are two "desired" issues (issue972, issue973) and one "optional" issue (issue975) left.

Regarding issue972, it's not really a migration issue given that we never tested Gurobi. It could be linked from existing Gurobi issues instead of from this one, if we have existing Gurobi issues, and then it could be removed from the summary of this issue.

Regarding issue973, the title is vague, but it looks like the open item there is the server-side hook question. Perhaps we should discuss this.

Regarding issue975, we've had some experience with github now, and I think it might again be a good time to discuss and perhaps close this. But we could also keep it open and mark this meta-issue as resolved if we decide to intentionally leave that decision for the future.

This is still open, but there is only one optional item left. Should we close this issue?

Branches are protected.

Add issue976 to summary.

Not sure where else this fits best, so let me mention it here:

- We have performed the hg->hg cleanup and hg->git conversion of our primary repository.
- The converted github repository is aibasel/downward.
- The airepos hg repository has been set to read-only. If you try to push, you'll receive an error.
- hg.fast-downward.org will remain available until the December 2020 release (2020.12), but it will reflect the frozen state of the hg repository. We left a note in our release process documentation so that this won't get forgotten.
- For now, we want to limit ourselves to pull requests for making changes to the primary github repository, but we haven't fully figured out the details of the desired workflow yet.

Add issue975 to summary.

Add TODO about protecting the "main" branch.

misc/uncrustify.py is gone now.

> Shouldn't we do this as part of issue969?

Fine by me.

> Remember to remove misc/uncrustify.py from the new git repo.

Shouldn't we do this as part of issue969?

Remember to remove misc/uncrustify.py from the new git repo.

Add links to new issues in the summary.

Regarding the naming conflict aibasel/downward, we decided that the main 
repository will live there and the release containers will move into this 
repository.

misc/release will become misc/releases and the release folders will go there 
(next to the release creation scripts).