Questions regarding co-creation
Expand | ||
---|---|---|
| ||
Github is an ideal place to work together with colleagues and also external parties. In the new organization https://github.com/Deltares-research, there are a few ways to work with outside collaborators:
|
Questions relating to migration
Expand | ||
---|---|---|
| ||
ProblemAfter your repository is moved from https://github.com/Deltares to the new organization https://github.com/Deltares-research, it is possible that you are required to re-authorize the OAuth Application when you perform a GIT action on the command line. SolutionFollow the following steps to refresh you authorization token:
|
Expand | ||
---|---|---|
| ||
After your repository is moved from https://github.com/Deltares to the new organization https://github.com/Deltares-research, the list of collaborators has been cleared. Each repository is assigned one administrator who is tasked with inviting new collaborators. Inviting new collaborator can be done by the Administrator using the 'Add people' button.
For bigger repositories it is advised to user teams instead of adding individual users. At present it is not possible for administrators to create a Team. In such cases the administrator should send a request to the Github support group: github-support@deltares.nl |
Questions relating to applications
Expand | ||
---|---|---|
| ||
In the current Deltares organization, co-pilot has been enabled. There are 24 licenses available, all of which are currently taken. At present co-pilot is not enabled in the Deltares-research organization. This will change once the Deltares organization has been added to the Deltares enterprise. How we plan to use co-pilot in the future and how we plan to manage the licenses has not yet been worked out. For more information please contact: github-owners@deltares.nl . |
Expand | ||
---|---|---|
| ||
Apparently some users can no longer see their repositories in Zenodo. Even when their repositories have not been moved from the Deltares organization. Why this is the case is still unclear however the resolution is that one of the organization owners logs into Zenodo using ones Github account and activates the required repositories. |