Advanced Settings

  • 3 minute(s) read
Prev Next

Advanced Settings

The Advanced Settings page provides fine-grained control over repository behavior, access rules, collaboration features, and integration options. These settings let you tailor how your repository is used, documented, reviewed, and managed across your organization.

Files

Controls access to the repository’s source code, commits, and branches.

Why this matters:
Restricting file visibility allows organizations to provide limited access to collaborators, external partners, or automated systems while protecting sensitive project data.

Wiki

Each repository can use either the built-in Wiki or link to an external documentation portal.

Why this matters:
Documentation needs vary—some teams use lightweight in-repo documentation, while others publish docs on external platforms (Document360, GitHub Pages, Confluence, etc.).

Enable Repository Wiki

Toggle the Wiki feature on or off. Disabling the Wiki hides the tab entirely.

Built-in Wiki Options

  • Default Wiki Branch Name – The branch used to store Wiki pages (default: master).
  • Default Access Permission – Controls which signed-in users can read or edit the Wiki.

External Wiki

Redirects the Wiki tab to an outside documentation site.

  • External Wiki URL – Destination for all Wiki navigation.

Issues

Configure how issue tracking works within the repository.

Why this matters:
Issue tracking is central to planning and execution. Whether you use AllSpice’s built-in system or connect to an external tracker, these options control how work is reported, tracked, and automated.

Enable Repository Issue Tracker

Turns the built-in issue tracker on or off.

Built-in Issue Tracker Options

  • Enable Time Tracking – Allow users to log estimated or actual time.
  • Let Only Contributors Track Time – Restricts time logging to contributors.
  • Enable Dependencies for Issues and Design Reviews – Allows linking issues to define sequencing or blockers.
  • Close an Issue via e-commit Made in a Non-default Branch – Allows commit messages in any branch to close issues (e.g., Fixes #123).

Use External Issue Tracker

Redirects all issue navigation to a third-party system (GitHub Issues, Jira, YouTrack, etc.).

External Issue Tracker Settings

  • External Issue Tracker URL
  • External Issue Tracker URL Format

Example format:
https://hub.allspice.io/{user}/{repo}/issues/{index}

Where:

  • {user} — username
  • {repo} — repository name
  • {index} — issue number extracted from commits or URLs

Issue Number Extraction

Defines how the system identifies issue numbers:

  • Numeric (#123)
  • Alphanumeric (ABC-123)
  • Regular Expression – Uses the first capture group as {index}.

Why this matters:
Different teams use different issue formats. Proper extraction ensures commits automatically link to the correct external issues.

Projects

Enable Projects

Turns on the Projects tab for planning, boards, milestones, or workflow management.

Projects Mode

Determines which types of projects are available or visible.

Why this matters:
Projects help organize work visually. Enabling or restricting project types ensures consistency with team workflows.

Releases

Enable Repository Releases

Enables the Releases tab for distributing compiled binaries, firmware, hardware files, or packaged assets.

Why this matters:
Releases provide a structured location for versioned build outputs, improving traceability and downstream consumption.

Packages

Enable Repository Package Registry

Allows the repository to host and publish packages (such as libraries, components, or build artifacts).

Why this matters:
Package registries simplify distribution and reuse of components across multiple projects.

Actions

Enable Repository Actions

Activates automated workflows such as CI/CD pipelines, testing, validation, and deployment scripts.

Why this matters:
Actions let you automate repetitive or critical tasks, improving reliability and reducing human error.

See Actions documentation

Design Reviews

Enable Repository Design Reviews

Turns on structured review workflows for hardware or software designs.

Why this matters:
Design Reviews provide formal review and sign-off mechanisms, essential for engineering teams that follow traceable development processes.

See Design Reviews

Merge Styles

Control how pull requests are merged into the repository.

Why this matters:
Different teams follow different merge philosophies. These settings let you enforce clean history, traceability, or fast-forward-only workflows depending on your development model.

Allowed Merge Methods

  • Merge Commit – Creates a merge commit preserving full history.
  • Rebase (fast-forward) – Rewrites commits on top of the target branch.
  • Rebase then Fast-Forward
  • Rebase then Create Merge Commit
  • Disable Squash Commit – Prevents squashing PRs into a single commit.
  • Fast-Forward Only – No merge commits allowed; requires linear history.
  • Manually Merged – Detects merges done outside the UI.

Default Merge Style

Specifies the default merge action shown when completing pull requests.

Additional Merge Options

  • Allow edits from maintainers by default
  • Enable updating design review branches by rebase
  • Delete design review branches after merge
  • Auto-detect manual merges
  • Ignore whitespace for conflict resolution