You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 13, 2025. It is now read-only.
Github's Teams are groups of organization members whereas Gitlab's Groups are just groups of Gitlab users (Groups are more like Github' organizations).
5
+
Each Github organization can have repositories and assign teams to them and each team can have subteams.
6
+
Gitlab groups can have repositories and create subgroups (nested).
7
+
8
+
## Setup guide
9
+
10
+
### Github
11
+
12
+
1. Go to 'https://github.com/settings/organizations' and click 'New organization' button
13
+
2. Select your plan.
14
+
3. Enter organization's name, contact email address, solve the captcha and click Next
15
+
4. Click 'Skip this step'
16
+
5. If you receive a survey, you can just go to the bottom and click Submit without filling anything.
17
+
6. On your new organization page go to 'Teams' tab and click 'New team' button.
18
+
7. Fill in your team's name, description (optional) and visibility. Submit by clicking 'Create team'.
19
+
Now you have your team created and you should get redirect to its page.
20
+
You can assign it to an organization's repository by clicking 'Add Repository' and entering repository's name, in 'Repositories' tab of a team's page.
21
+
22
+
### Gitlab
23
+
24
+
1. Go to 'https://gitlab.com/dashboard/groups' and click on 'New group' button.
25
+
2. Enter group's name and set visibility level. Finish by clicking 'Create group'.
26
+
You can now create repositories for this group or subgroups.
27
+
28
+
## Roles
29
+
30
+
In Topcoder X you can select role which user who joins via specific invitation link receives.
31
+
32
+
### Github
33
+
34
+
For github team you can set two roles: Member and Maintainer.
35
+
You can read about them here: https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization and https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member
36
+
37
+
### Gitlab
38
+
39
+
For gitlab group you can set five roles: Guest, Reporter, Developer, Maintainer, Owner
40
+
You can read about them here: https://docs.gitlab.com/ee/user/permissions.html
Copy file name to clipboardExpand all lines: src/assets/WorkingWithTickets.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ The basic flow for handling a ticket is as follows:
4
4
5
5
1. Assign the ticket to yourself, and the system will change the label to "tcx_Assigned", removing the "tcx_OpenForPickup" label. Please only assign tickets to yourself when you are ready to work on it. I don't want tickets assigned to someone and then not have them work on a ticket for 24 hours. The goal here is a quick turnaround for the client. If you can't work on a ticket immediately, leave it for someone else.
6
6
7
-
1. Complete the ticket and create a merge request within 24 hours. Please ensure your merge request can be merged automatically (resolving any conflicts) and that it's against the latest commit in Git when you create it.
7
+
1. Complete the ticket and create a merge request within 24 hours. Please ensure your merge request can be merged automatically (resolving any conflicts) and that it's against the latest commit in Git when you create it.
8
8
9
9
1. Change the label on the ticket to "tcx_ReadyForReview"
10
10
@@ -24,7 +24,7 @@ If a fix is rejected, a comment, and possibly a screenshot, will be added to the
24
24
25
25
# Payment amounts
26
26
27
-
Each ticket in GitLab has a dollar value. That is the amount you will be paid when the ticket is completed, merged, and verified by the copilot. Note that there is still a 30 day waiting period as the payment will be treated as a regular TopCoder challenge payment.
27
+
Each ticket in Gitlab / Github has a dollar value. That is the amount you will be paid when the ticket is completed, merged, and verified by the copilot. Note that there is still a 30 day waiting period as the payment will be treated as a regular TopCoder challenge payment.
28
28
29
29
# Important Rules:
30
30
@@ -40,6 +40,6 @@ Each ticket in GitLab has a dollar value. That is the amount you will be paid w
40
40
41
41
- If an assigned task is not done in 24 hours, you will need to explain why it is not completed as a comment on the ticket.
42
42
43
-
- You can ask questions directly on the GitLab ticket.
43
+
- You can ask questions directly on the Gitlab / Github ticket.
44
44
45
-
### ANYONE NOT FOLLOWING THE RULES ABOVE WILL BE WARNED AND POTENTIALLY LOSE THEIR GITLAB ACCESS!
45
+
### ANYONE NOT FOLLOWING THE RULES ABOVE WILL BE WARNED AND POTENTIALLY LOSE THEIR GIT ACCESS!
0 commit comments