-
Notifications
You must be signed in to change notification settings - Fork 2
Workflow
Hannes Datta edited this page Mar 21, 2022
·
13 revisions
When working on (empirical) projects, we always work in GitHub repositories. See also here.
-
All of our code is publicly available on GitHub.
- If there is no repository yet for the project you are working on, create one in the Tilburg Science Hub organization.
- If a repository already exists, fork it under the Tilburg Science Hub organization.
-
The repository is "the final product"
- i.e., our deliverables will consist of code/files committed on GitHub, and not individually exchanged data files with "results". Code files also need to be committed as such (and not "zipped" in a conversation on the Issue page).
-
We keep all of our communication on GitHub (use Issues); only if needed, you can take the communication to other channels (e.g., Teams or email, such as when arranging appointments, etc.).
Wonder how to collaborate on projects using GitHub? Check it out here!.
- Home
- Our organization
- Our core values
- Getting organized
- Working on Projects
- Contributing to the TSH website
- Notes for Deboarding