Proposal: Rename repository to "blender-manual" #104380
Labels
No Label
Meta
Good First Issue
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Eevee & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds, Tests & Devices
Module
Python API
Module
Rendering & Cycles
Module
Sculpt, Paint & Texture
Module
User Interface
Module
VFX & Video
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-manual#104380
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Documentation is a vague term, and there are different kinds of documentation for Blender. Namely, the manual, the developer documentation and the Python API reference. A new infrastructure for developer documentation is also being investigated, which would probably use a Git repository as well.
This repository is meant for the Blender manual, and I propose we also call it that way.
blender-manual would be a name consistent to the other repositories in the Blender organization: https://projects.blender.org/blender.
It probably makes sense to do this switch together with the SVN -> Git transition.
I agree, I have access to rename the rename the repository. I assume this would create the necessary redirects like other platforms.
I tried a quick search in the Gitea docs and could not anything that would confirm or deny this assumption.
Closed as resolved