Module 2 Exercise 5

1. Will you keep all course materials in a repository? Or just assignments?
I would keep assignments in the repository. We use Canvas for our LMS and I would want to keep their instructional materials, class agendas and tests within Canvas.

2. When will you expect students to commit?
I’d like them to commit as they go and when they’re finished with each assignment.

3. What sort of commit messages should they use?
Detailed, specific messages outlining what they’ve done in the code.

4. When do you want your students to push their code to GitHub?
It would be great to see their progress as they go.

1. Will you keep all course materials in a repository? Or just assignments?

All course materials will be available via Github repos.

2. When will you expect students to commit?
As often as logical possible - so whenever an other feature has been implemented.

3. What sort of commit messages should they use?

Describing the new features - not exactly the changes in code (that would be diffable). But as I might use submit50 from @CS50 this might not be so easy.

4. When do you want your students to push their code to GitHub?

I would like to see Pushs often, so data loss is not an problem/excuse.

  1. Course materials : Repository or Assignments ?

The course available are mainly Jupyter Notebook available on Github. I want them to complete each training sheet in a first time. As for the project, I will choose repository. So both.

  1. Commit Frequencies ?
    As much as needed for them. For the project, they are a team and it’s a good way to communicate between them and for me to supervise and help them.

  2. What sort of commit messages should they use?

A define title ‘New Feature’, ‘Refrac’, ‘Doc’, … with a bullet list of notable change (not more than three changes to avoid damage in case of reverse.

  1. When do you want your students to push their code to GitHub ?

As much as they can, the remote repository is a direct way to communicate between them.

Thanks to the previous personn for the answer format :smiley:

  1. Will you keep all course materials in a repository? Or just assignments?
    All material will be available on my repositories.
  2. When will you expect students to commit?
    Frequently, as they finish each exercise.
  3. What sort of commit messages should they use?
    The submitted exercise.
  4. When do you want your students to push their code to GitHub?
    When they complete the whole assignment.

My dashboard …

Exercise: Workflow

  1. I’ll be keeping all course materials in a repo
  2. I don’t have expectations on when to commit, but I do want them to be able to finish and push a project in 30 days
  3. Commit messages should be able to convey the main idea of any improvements on that commit
  4. 30 days

  1. Will you keep all course materials in a repository? Or just assignments?

Most of our materials have source code associated with it, so that will be in here. Most assignments do have source code required as well, so that will be in here as well. There are other materials like videos that I do not see how we would could keep here.

  1. When will you expect students to commit?

they will join Day 1 and probably commit Week 1 and as often there after.

  1. What sort of commit messages should they use?

We always stress meaningful messages that describe the changes in the files/features/functionality

  1. When do you want your students to push their code to GitHub?

Week 1 so that they can share code with others not just instructors.

1. Will you keep all course materials in a repository? Or just assignments?
When I’ve used classroom & github in the past, it’s just assignments that I keep in repos.

2. When will you expect students to commit?
I ask that they make commits at “meaningful” stages of completing the assignment. For some assignments, I ask for very specific commit points, others are left up to the student’s discretion.

3. What sort of commit messages should they use?
They need to have something that accurately represents what changes have been made.

4. When do you want your students to push their code to GitHub?
I encourage them to do this often since it provides, in essence, a backup of their work, but I don’t require it except at the “end”.

Hiya @nicschwartz just writing in to let you know that we’ve shipped the ability to use GitHub Classroom with Canvas. Here’s how:

1 Like

:heartpulse:

1. Will you keep all course materials in a repository? Or just assignments?
I would keep all course materials in the repository. Code and slides.

2. When will you expect students to commit?
I’d like them to commit as they go and when they’re finished with each assignment.

3. What sort of commit messages should they use?
Pretty detailed, specific messages outlining what they’ve done in the code.

4. When do you want your students to push their code to GitHub?
It would be great to see their progress as they go. Mandatory at some key points during the course and of course at the end.

Here is my screenshot.

Regards

Frans Bleeker

1. Will you keep all course materials in a repository? Or just assignments?
Just Assignments, I will share other resources on Google Classroom

2. When will you expect students to commit?
Depends on the assignment. Some are pretty short so just once. For long ones more that once for sure.

3. What sort of commit messages should they use?
Long enough. I will let them know after I read them if they are not appropriate

4. When do you want your students to push their code to GitHub?
See 2.

1. Você manterá todos os materiais do curso em um repositório? Ou apenas atribuições?

Todos os materiais do curso serão mantidos nos repositórios do Github.

2. Quanto você espera que os alunos se comprometam?
O mais breve possível - sempre que um recurso for implementado.

3. Que tipo de mensagem de confirmação eles devem usar?

Descrevendo os novos recursos implementados.

4. Quando você deseja que seus alunos enviem seus códigos para o GitHub?

Gostaria de ver as publicações frequentemente, para que não haja dúvidas na execução das atividades.

Here’s mine…

© 2017 GitHub, Inc.
with by
GitHub Education