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

Git Branch TODO #1855

Closed
SoftwareDev opened this Issue Oct 26, 2014 · 6 comments

Comments

Projects
None yet
3 participants
@SoftwareDev
Contributor

SoftwareDev commented Oct 26, 2014

// Migrated from past issues

Goals:

  • Figure out how to authenticate on the command line (LDAP?)
  • students should be able to use git on the command line to interface with their repos
  • students should have to authenticate themselves on the command line
    - Manage permissions in Gitolite like in svn

Tasks:

Completed Tasks:

  • Web interface is complete.
  • All tests passing as of Jan 19, 2015

Icebox:

This was referenced Oct 26, 2014

@SoftwareDev

This comment has been minimized.

Show comment
Hide comment
@SoftwareDev

SoftwareDev Dec 21, 2014

Contributor

#1952

The Git branch has a fully functioning web-interface for students and admins to view repositories and interact with them.

The next steps is to look into Gitolite (which is mentioned here https://github.com/MarkUsProject/Markus/wiki/GitBackEnd) so that students can interact with their repos remotely and from the command-line.

There will need to be some considerations into how students will authenticate with their repos (public/private keys) and some new views will be needed to manage this when Git is the selected source control system for the Markus instance.

Contributor

SoftwareDev commented Dec 21, 2014

#1952

The Git branch has a fully functioning web-interface for students and admins to view repositories and interact with them.

The next steps is to look into Gitolite (which is mentioned here https://github.com/MarkUsProject/Markus/wiki/GitBackEnd) so that students can interact with their repos remotely and from the command-line.

There will need to be some considerations into how students will authenticate with their repos (public/private keys) and some new views will be needed to manage this when Git is the selected source control system for the Markus instance.

@david-yz-liu

This comment has been minimized.

Show comment
Hide comment
@david-yz-liu

david-yz-liu Dec 21, 2014

Contributor

There's one outstanding issue I just noticed - if a submission has been collected, you can't go back and collect a different revision. The old collected submission stays there permanently.

Contributor

david-yz-liu commented Dec 21, 2014

There's one outstanding issue I just noticed - if a submission has been collected, you can't go back and collect a different revision. The old collected submission stays there permanently.

@SoftwareDev

This comment has been minimized.

Show comment
Hide comment
@SoftwareDev

SoftwareDev Jan 16, 2015

Contributor

@david-yz-liu I'm a little confused as to how to reproduce this. I loaded up an clean instance of MarkUs on the git branch and waited for A1 to be due and collected all submissions. Then I manually went back to the student's repo and collected one of the first submissions (with no files). After that, the collected submission for grading looked like the right one.

Contributor

SoftwareDev commented Jan 16, 2015

@david-yz-liu I'm a little confused as to how to reproduce this. I loaded up an clean instance of MarkUs on the git branch and waited for A1 to be due and collected all submissions. Then I manually went back to the student's repo and collected one of the first submissions (with no files). After that, the collected submission for grading looked like the right one.

@david-yz-liu

This comment has been minimized.

Show comment
Hide comment
@david-yz-liu

david-yz-liu Jan 16, 2015

Contributor

@SoftwareDev Yup, you're right. I can't reproduce the issue any more.

Contributor

david-yz-liu commented Jan 16, 2015

@SoftwareDev Yup, you're right. I can't reproduce the issue any more.

@reidka

This comment has been minimized.

Show comment
Hide comment
@reidka

reidka Apr 26, 2016

Member

This one is really done.

Member

reidka commented Apr 26, 2016

This one is really done.

@reidka reidka closed this Apr 26, 2016

@SoftwareDev

This comment has been minimized.

Show comment
Hide comment
@SoftwareDev

SoftwareDev Apr 30, 2016

Contributor

It is amazing to see this finally completed! Great job all!

-Alex

[image: --]
Alexander Grenier
[image: https://]alexgrenier.ca
https://about.me/alexander.grenier?promo=email_sig

On Tue, Apr 26, 2016 at 11:36 AM, Karen Reid notifications@github.com
wrote:

This one is really done.


You are receiving this because you were assigned.
Reply to this email directly or view it on GitHub
#1855 (comment)

Contributor

SoftwareDev commented Apr 30, 2016

It is amazing to see this finally completed! Great job all!

-Alex

[image: --]
Alexander Grenier
[image: https://]alexgrenier.ca
https://about.me/alexander.grenier?promo=email_sig

On Tue, Apr 26, 2016 at 11:36 AM, Karen Reid notifications@github.com
wrote:

This one is really done.


You are receiving this because you were assigned.
Reply to this email directly or view it on GitHub
#1855 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment