openmw.org

From now on we will be using the OpenMW org repository on github instead of mine. That is: https://github.com/OpenMW/openmw

Developers should direct pull requests to this repository from now on and each developer also needs to adjust the URL of their upstream remote (or whatever they are using to pull from my github repository) via
Currently open pull requests towards my old repository does not need to be replaced.

Beyond that nothing should change. If it does, start beating on BrotherBrick, because he was the one who pushed the idea of moving the repository to the organisation.

I will begin adjusting the documentation in a bit. If you still see any references to my old repository in an hour from now, please help out with fixing that.

I would like to add that the following url is correct, at least for me (and I suspect other people with read-only access): Oh and for people who are new to git, to modify the remote, do the following:

If you've forked and are working on the master branch this will bring you up to date:
You only need to use the -f the first time.

Or in one line (can we edit that into the start post?):
Rebase and force-push is completely unnecessary.

Edit done.

scrawl wrote:Or in one line (can we edit that into the start post?):

Code: Select all

git remote set-url upstream https://github.com/OpenMW/openmw.git

Rebase and force-push is completely unnecessary.

Ah thanks for that!

It could be useful for rebasing different branches though. i.e. test branch and master

The github irc bot still uses the old repo.

And "fork me on github" link on openmw.org.

https://bugs.openmw.org/projects/openmw/repository not picking up new commits.

There's something wrong with permissions. I can't push nor accept pull requests in OS X deps repo (https://github.com/OpenMW/homebrew-openmw/).

That's kinda weird since I'm in "Core team" group.

UPD: disregard that, that's the pubkey issues, and PR can't be merged from web because of, you know, conflicts.