MarkUs Blog

MarkUs Developers Blog About Their Project

Archive for the ‘git’ tag

Git Project

without comments

I plan to work on the git backend branch for the month of March (and beyond).

I’ve created a branch of the wiki (https://github.com/munrocape/Markus/wiki/GitBackEnd) in the hopes of having a more concise and detailed set-up guide for future developers as I personally unlinked/mixed up my symbolic links for ruby and it required a fresh virtual box. Oops!

Written by Zach Munro-Cape

March 7th, 2014 at 12:19 am

Closing GitHub Issues

without comments

We’ve just moved to GitHub, and one of the main differences from Dr. Project is that we only allow a few core members to push to the official MarkUs repository.

A side-effect:  only users with push permissions on the MarkUs repository can close issues.

So how do developers close issues if they don’t have permission to do it?  GitHub actually gives us a neat mechanism to do this.  Here’s the workflow:

  1. Find an an issue on GitHub, and work on it on your fork.
  2. Once your work is done, commit to your fork with the commit message containing “closes #<issue number>”.  Without the <> symbols.
  3. Make a pull request
  4. Once the MarkUs core developers merge your patch in, GitHub will automatically close the issue.

Easy as pie.

More information here.

Written by m_conley

October 15th, 2010 at 2:59 pm

Posted in Developer Essentials

Tagged with , , ,