4Geeks.com academy portal can now automatically and optionally sync students as users of your Github organization.
🐞 This is a beta feature that will be tested within the following weeks.
We have taken steps to activate the GitHub sync in the current 4Geeks Academy locations in the system. This can be disabled at any time in the admin Github settings.
Students are automatically added
to the GitHub organization in the following situations:
active
.You can also manually invite students to the organization from Github.com and 4Geeks.com will notice them when synching with Github; it will try fetching their cohorts and connecting them to your academy.
⚠️ If a user is found in a Github organization but is not reflected as a 4geeks.com user and does not belong to any cohort, the system will mark the user as ignored.
Students that were removed
from the GitHub organization in the following situation:
active
status in a cohort.You can also manually delete users on Github, but the system will probably add them back. It is recommended to mark them as deleted on the GitHub admin page and wait for the system to delete them from the GitHub Organization.
⚠️ Cohorts that
never end
are also considered; as long as the student is active, they will be allowed into the academy organization.
Students will get invitations to join our Github organization, if they don't accept the invite they will never be a part of your organization, and won't have access to features like: Accessing private repositories, free usage of Github Codespaces at the academy repositories, etc.
4Geeks.com will automatically add/remove users based on cohort activity but you should always be aware of the changes being made and make sure your students are proparly being added and removed.
For logistical reasons and because a student can belong to several academies, we have decided to avoid synchronizing in real-time; the synchronization will occur in a batch process every few minutes. The exact interval is to be determined.
What if students in never ending cohorts don't graduate and stay active
forever?
The system will keep asuming the student belongs to your academy. It will stay forever inside your github organization. You can always manually deleted the student from the administration panel.
What if the user is in multiple cohorts but gets deleted from one?
The system will ensure it only gets deleted from the GitHub organization if it loses the status as active
in all the cohorts.
What if the user is in multiple academies?
If the user is in multiple cohorts in multiple academies, we will only consider those cohorts where the student is still active.