Module issue 

Starting work from a forge issue: the pure half.

An issue becomes a branch name at the forge, never in this binary’s imagination. GitHub names the branch server-side, so nothing here renders one. GitLab exposes no such endpoint — its branch-name template is a project setting the web UI applies — so rk reproduces Issue.to_branch_name exactly, and this module is where that reproduction lives. Spawning stays in the handler, exactly as crate::branches declares for the branch half.

Structs

Ask

What one call asks the forge for.

Reference

What the operator named, and where it points.

Rendered

A rendered branch name, and whether any character fell outside the transliteration table.

Resolved

What one issue resolves to, before anything is seated.

Enums

Minted

What the forge already carries for one issue.

Constants

GITLAB_DEFAULT_TEMPLATE

GitLab’s documented default when a project sets no template.

Functions

admissible

Whether the landed grammar admits a branch name.

agrees

Whether a reference names the clone the verb was pointed at.

gitlab_branch_name

Render a GitLab branch name for one issue, the way GitLab renders it.

linked_branch

Read a GitHub linkedBranches answer.

links_to

Whether GitLab links a branch of this name to the issue.

parameterize

Rails String#parameterize, the one GitLab calls.

parameterize_reporting

parameterize, reporting whether the transliteration table covered every character it was given.

parse_reference

Parse what the operator typed into the issue it names.

resolve

Resolve one issue to its branch, minting at the forge under apply.