我在哪里可以管理上传到 Gitlab.com 项目维基的文件？
Where can I manage files uploaded to wiki of a Gitlab.com project?
我在为我的私人项目创建 wiki 时上传了一些文件到我在 "gitlab.com" 上的 Gitlab 存储库。
现在我的问题是：
- 我可以查看已上传文件的列表吗？
- 有什么方法可以删除其中的一些吗？
- 为什么上传文件的权限是public？我可以将其更改为私有吗？
gitlab当前版本为企业版8.9.4-ee。
通过 wiki 编辑器的附件上传到 /uploads/。从 GitLab 版本 8.9.0 开始，您无法管理这些文件（即删除它们）。
如果您想自己管理这些文件，您可以将 wiki 克隆为存储库。您可以在 Wiki -> Git Access 中找到克隆 URL。它应该看起来像这样：git@<link to gitlab>:<group/user name>/<project name>.wiki.git。在那里你可以把你的图片和 link 它们放在你的 wiki 中。图片的 link 是相对于 repo root 的，所以如果你的图片 image.png 在根文件夹中，你可以 link 像这样 .
权限明智的这些文件将只对至少具有来宾访问您的项目的用户可见，即使他们具有直接 link.
对于 GitLab 11.3 及更高版本，可以通过克隆 wiki 存储库（从右侧栏上的 link）并导航到 /uploads 文件夹来找到和更改任何附加到 wiki 页面的文件在本地回购协议中。变化可以上推
文件存储位置
Attach a file, and GitLab stores it according to your installed version of GitLab:
- Files added in GitLab 11.3 and later: Files are stored in the wiki’s Git repository.
- Files added GitLab 11.2 and earlier: Files are stored in GitLab itself. To add the file to the wiki’s Git repository, you must re-upload the file.
GitLab - Create a new wiki page
如何获取 wiki 的本地仓库
Wikis are based on Git repositories, so you can clone them locally and edit them like you would do with every other Git repository. To clone a wiki repository locally, select Clone repository from the right-hand sidebar of any wiki page, and follow the on-screen instructions.
GitLab - Create or edit wiki pages locally
限制可以查看 wiki 页面的用户
目前无法限制 users/groups 在 GitLab wiki 上可以看到的页面。有一个GitLab issue推荐这个功能。这扩展到 wiki 存储库中的文件。
Wikis are based on Git repositories, so you can clone them locally and edit them like you would do
实际上...参见 GitLab 14.0（2021 年 6 月）
Edit wiki pages with the WYSIWYG Markdown editor
Edit wiki pages with the WYSIWYG Markdown editor
Editing wiki content could be so much easier! Many GitLab wikis use Markdown formatting, and for some users, Markdown is a barrier to efficient collaboration. In this release, you now have access to a rich, modern Markdown editing experience in your wiki, so you can edit with confidence.
Instant feedback and visual editing tools help make wiki editing more intuitive, and remove barriers to collaboration. GitLab saves the changes as Markdown when you’re done, so users who want to edit the Markdown directly can do so. You can even type Markdown into the new editor and it will automatically format the text as you type.
GitLab 14.0 introduces the Content Editor into the Wiki with support for most of the basic Markdown content types like headers, bold and italic text, lists, code blocks, and links. Full support for the entire GitLab Flavored Markdown specification will arrive in upcoming releases. We also plan to make the Content Editor available in other areas of GitLab in the future. We welcome input on this early MVC in this feedback issue.
See Documentation and Epic.
是的，包括 page deletion。
或者：
参见 GitLab 14.2（2021 年 8 月）
Upload and attach files in the new wiki editor
GitLab 14.1 introduced the ability to upload and insert images into the new wiki content editor.
Now in GitLab 14.2, you can upload and attach .zip, .pdf, .txt, and other binary files in the same way.
This brings us one step closer to feature parity with the classic wiki editor, and unlocks additional ways for you to collaborate on rich content in your wiki pages.
See Documentation and Issue.
参见 GitLab 14.9（2022 年 3 月）
Render pasted Markdown in the wiki WYSIWYG editor
Markdown content destined for your GitLab wiki is sometimes created outside of GitLab.
In the “classic” wiki editor, you can paste valid Markdown with no problem, because you are working with the raw source. The page only renders when you submit the content.
In the wiki WYSIWYG editor, however, your clipboard’s content might have been pasted in as plain text, forcing you to manually reformat every line to remove Markdown syntax and re-format it using the WYSIWYG tools.
In GitLab 14.9, the Markdown content you paste into the WYSIWYG editor using Command / Control + V is parsed and rendered as rich text.
You can still force the content to paste as plain text using Command / Control + Shift + V.
See Documentation and Issue.
我在为我的私人项目创建 wiki 时上传了一些文件到我在 "gitlab.com" 上的 Gitlab 存储库。
现在我的问题是：
- 我可以查看已上传文件的列表吗？
- 有什么方法可以删除其中的一些吗？
- 为什么上传文件的权限是public？我可以将其更改为私有吗？
gitlab当前版本为企业版8.9.4-ee。
通过 wiki 编辑器的附件上传到 /uploads/。从 GitLab 版本 8.9.0 开始，您无法管理这些文件（即删除它们）。
如果您想自己管理这些文件，您可以将 wiki 克隆为存储库。您可以在 Wiki -> Git Access 中找到克隆 URL。它应该看起来像这样：git@<link to gitlab>:<group/user name>/<project name>.wiki.git。在那里你可以把你的图片和 link 它们放在你的 wiki 中。图片的 link 是相对于 repo root 的，所以如果你的图片 image.png 在根文件夹中，你可以 link 像这样 .
权限明智的这些文件将只对至少具有来宾访问您的项目的用户可见，即使他们具有直接 link.
对于 GitLab 11.3 及更高版本，可以通过克隆 wiki 存储库（从右侧栏上的 link）并导航到 /uploads 文件夹来找到和更改任何附加到 wiki 页面的文件在本地回购协议中。变化可以上推
文件存储位置
Attach a file, and GitLab stores it according to your installed version of GitLab:
- Files added in GitLab 11.3 and later: Files are stored in the wiki’s Git repository.
- Files added GitLab 11.2 and earlier: Files are stored in GitLab itself. To add the file to the wiki’s Git repository, you must re-upload the file.
GitLab - Create a new wiki page
如何获取 wiki 的本地仓库
Wikis are based on Git repositories, so you can clone them locally and edit them like you would do with every other Git repository. To clone a wiki repository locally, select Clone repository from the right-hand sidebar of any wiki page, and follow the on-screen instructions.
GitLab - Create or edit wiki pages locally
限制可以查看 wiki 页面的用户
目前无法限制 users/groups 在 GitLab wiki 上可以看到的页面。有一个GitLab issue推荐这个功能。这扩展到 wiki 存储库中的文件。
Wikis are based on Git repositories, so you can clone them locally and edit them like you would do
实际上...参见 GitLab 14.0（2021 年 6 月）
Edit wiki pages with the WYSIWYG Markdown editor
Edit wiki pages with the WYSIWYG Markdown editor
Editing wiki content could be so much easier! Many GitLab wikis use Markdown formatting, and for some users, Markdown is a barrier to efficient collaboration. In this release, you now have access to a rich, modern Markdown editing experience in your wiki, so you can edit with confidence.
Instant feedback and visual editing tools help make wiki editing more intuitive, and remove barriers to collaboration. GitLab saves the changes as Markdown when you’re done, so users who want to edit the Markdown directly can do so. You can even type Markdown into the new editor and it will automatically format the text as you type.
GitLab 14.0 introduces the Content Editor into the Wiki with support for most of the basic Markdown content types like headers, bold and italic text, lists, code blocks, and links. Full support for the entire GitLab Flavored Markdown specification will arrive in upcoming releases. We also plan to make the Content Editor available in other areas of GitLab in the future. We welcome input on this early MVC in this feedback issue.
See Documentation and Epic.
是的，包括 page deletion。
或者：
参见 GitLab 14.2（2021 年 8 月）
Upload and attach files in the new wiki editor
GitLab 14.1 introduced the ability to upload and insert images into the new wiki content editor.
Now in GitLab 14.2, you can upload and attach
.zip,.txt, and other binary files in the same way.
This brings us one step closer to feature parity with the classic wiki editor, and unlocks additional ways for you to collaborate on rich content in your wiki pages.
See Documentation and Issue.
参见 GitLab 14.9（2022 年 3 月）
Render pasted Markdown in the wiki WYSIWYG editor
Markdown content destined for your GitLab wiki is sometimes created outside of GitLab.
In the “classic” wiki editor, you can paste valid Markdown with no problem, because you are working with the raw source. The page only renders when you submit the content.
In the wiki WYSIWYG editor, however, your clipboard’s content might have been pasted in as plain text, forcing you to manually reformat every line to remove Markdown syntax and re-format it using the WYSIWYG tools.
In GitLab 14.9, the Markdown content you paste into the WYSIWYG editor using Command / Control + V is parsed and rendered as rich text.
You can still force the content to paste as plain text using Command / Control + Shift + V.
See Documentation and Issue.