Skip to content
@T-Craft-Platforms

T-Craft Platforms

Non-commercial, open-source, primarily Minecraft-based software and infrastructure, developed collaboratively.

T-Craft Platforms

T-Craft Platforms is a collaborative initiative primarily focused on building Minecraft plugins, mods, and the infrastructure required to run them on servers. The organization aims to keep projects open-source whenever possible.

🤝 Community & Conduct

  • Be respectful, constructive, and professional.
  • Assume good intent and communicate openly.
  • Follow common open-source etiquette.

🔐 Repository Visibility & Ownership

  • Create repositories as private/internal first if you are unsure.
  • If you want to mark a repository as internal only (only visible for members), you must:
    1. Mark the repository as private
    2. Add the @Everyone team with at least Read access
  • Only set a repository to public if you are sure it is intended for open-source.
  • Never make a repository public if it:
    • Uses proprietary software
    • Depends on private or demo environments
  • If a repository's purpose cannot be justified, it may be archived or removed at any time at the discretion of the organization administrators.
  • Do not migrate repositories to or away from T-Craft Platforms without prior approval from the relevant code owners and organization administrators.

🌿 Branching & Workflow

  • Pushing directly to main is discouraged, especially on public repositories.
    • For public and internal repositories, a branch protection rule protecting at least the default branch is highly advised.
    • For private repositories, branch protection is the responsibility of the repository maintainers, but is also highly advised.
  • Use the GitHub Issues Workflow correctly:
    1. Create an issue
    2. Create a branch linked to that issue
    3. Open a pull request
    4. Merge into main after review
  • Use branch name prefixes whenever possible:
    • feature/
    • bug/
    • security/
  • Avoid loose or unnamed branches.

🧩 Issues, Projects & Discussions

Issues

  • Use repository issues for detailed, specific feature requests or tasks.
  • Always consider:
    • Is this limited to one repository?
    • Or does it affect multiple repositories?

Projects

  • Use GitHub Projects (Kanban recommended) for planning and tracking.

Discussions

Use Discussions for:

  • Announcements
  • Ideas and coarse feature requests
  • Polls
  • Questions & answers

🖼️ Visual Guidelines

Selecting a Project for an Issue

Screenshot

Creating a Branch for an Issue

Screenshot
Screenshot
Screenshot

Pinned Loading

  1. .github .github Public

    Central hub for organization-wide coordination, rules, and onboarding.

Repositories

Showing 9 of 9 repositories

Top languages

Loading…

Most used topics

Loading…