Databases
StackOverflow2013
Postsdbo
POGit/Github workflow for students and projects
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGit/Github workflow for students and projects
    primarykey
    data
    text
    <p>Some fellow students and I are trying to introduce other students to git/Github and holding seminars has never really worked to get students excited and to start taking advantage of the tool and service. This year we want to try and work it into the course by having students use git to submit their projects for grading.</p> <p>The problem is; we have yet to come up with a proper work flow to do this. Ideally all this could be accomplished via Github. Our school has <em>Github Enterprise</em> (read unlimited public/private repos) so we have some room to play around. I'm not sure how much customization we can do, I'm not really sure what all Github Enterprise provides in that are either.</p> <p>My first workflow was as follows.</p> <ul> <li>Teaching Assistant posted a repo with starting code and the project description/assignment</li> <li>Students fork the repo to a private repository (I have a feeling this is not possible)</li> <li>Students work on their project individually</li> <li>When a student is ready to submit their project, they submit a Pull Request back to the Teaching Assistant.</li> </ul> <p>I'm pretty sure there are a few flaws in this, one being that we want to try and keep the students work private. Forking to a private repo may not be possible, and the pull request I'm sure would not work.</p> <p>I'm curious if someone has done something similar or has any ideas. I'm also willing to setup a separate server. My thinking here would be that students could use Github (private repos) to centralize their code and get familiar with Github by forking the project and working from there. When it comes to submitting their project for grading they would then push the project to a separate server. I'm not entirely sure how this would work, but I figure there would be some way to allow for accepting push request and pushing them into different branches via a hook.</p> <p>The idea is that having students work with git/github for the project might get them to start using version control in general for actually working on their project. Granted there are going to be the students that won't commit anything till they are finished anyways. This is more about exposing students to the technology.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UStravis
    1. UStravis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGit/Github workflow for students and projects
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGit/Github workflow for students and projects
      1. This table or related slice is empty.
      1. VTDownMod
    1. COI do not see what using github adds for what you presumably want to teach (e.g. using modern version control). Teach them *git* instead of *github* and let them email a patch series (e.g. even with `git send-email` if you give them a howto at the start). That way all the problems with private/non-private repos just go away since their clones are in their control and not tied to some predetermined workflow.
      singulars
      1. POGit/Github workflow for students and projects
      1. USBenjamin Bannier
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload