Investigate migration WOT-terms from Docusaurus to Spec-Up-T
Closed this issue · 2 comments
Investigate migration WOT-terms from Docusaurus to Spec-Up-T.
Questions:
- Is it possible to create a connection between Google Sheets and Spec-Up-T and load metadata?
- Is it possible to create a filter like the current one?
An option to eat our own dogfood a bit more: limit the user right of the wiki source management of the glossary:
How can I restrict the user right of wiki users editing wiki .md files
ChatGPT
To control who can edit wiki .md files in a GitHub repository, you need to manage user permissions at a repository level. GitHub doesn’t have granular control over wiki permissions separately from the repository permissions, so the following approaches can help you manage and restrict access effectively:
- Manage Repository Permissions
Set Repository Permissions
Go to Repository Settings:
Navigate to the GitHub repository where the wiki is located.
Click on the Settings tab.
Manage Access:
On the left sidebar, click Manage access under the Access section.
Adjust User Permissions:
Click Invite teams or people to add new collaborators or teams.
You can assign them different roles:
Read: Can view but not modify the repository or wiki.
Triage: Can manage issues and pull requests but has limited write access.
Write: Can push to branches, which affects the repository and wiki.
Maintain: Can manage repository settings but not sensitive information.
Admin: Full control over the repository, including managing permissions and settings.
Adjust Permissions for Existing Collaborators:
Click on a collaborator’s or team’s name to change their permission level as needed.
2. Restrict Wiki Access
Since the wiki is part of the repository, permissions applied to the repository also apply to the wiki. If you want to limit who can edit the wiki, you need to adjust the permissions of the repository:
Restrict Write Access:
Ensure that only trusted users or teams have write access to the repository. This will prevent unauthorized changes to the wiki since wiki edits are controlled by repository permissions.
Create Separate Teams:
Use GitHub Teams to manage different levels of access. Create specific teams for users who should have access to edit wiki pages and others who should not.
Use Branch Protection Rules:
While this primarily affects code branches, ensure that wiki edits are controlled indirectly by the repository's branch protection rules and permissions.
3. Consider External Wiki Platforms
If GitHub’s built-in wiki permissions are insufficient for your needs, consider using an external wiki platform with more granular permissions. You can link this external wiki to your GitHub repository or host it separately.
Summary
Adjust Repository Permissions: Control who can edit wiki .md files by managing the repository’s permission settings. Limit write access to trusted users or teams.
Use GitHub Teams: Create and manage teams to control access levels more effectively.
Consider External Solutions: For more granular control, explore external wiki platforms if GitHub’s default settings do not meet your needs.
By configuring these settings, you can better manage who has the ability to edit wiki pages in your GitHub repository.
onhold