Allocate a part number

GitMCloud can allocate a part number from the shared registry (.gitm/partnumbers.json) without SolidWorks. It cannot stamp the number into the file — that requires GitM with the file open.

Prerequisites

• Signed in and connected.
• Engineer role (GitHub write) or above.

How allocation works

• GitMCloud uses the same allocation algorithm as GitM (an exact port), so numbers stay collision-compatible across both tools.
• Allocation is a compare-and-swap (CAS) write to .gitm/partnumbers.json on GitHub, retried on conflict.
• The new entry is marked stamped: false, meaning the number exists in the registry but has not yet been written into the SolidWorks file's property.
• Uniqueness is keyed on (path, config), not path alone. A single-config file uses an empty config; "Default" is treated the same as empty.

Allocate

1. On the Files tab, right-click the file → allocate a part number.
2. GitMCloud writes the number to the registry.

Finishing the stamp (in GitM)

Because GitMCloud can't open the file, the number stays stamped: false until GitM reconciles it: the next time the file is open in SolidWorks, GitM stamps the number into the file's part property and flips it to stamped. See Manage part numbers.

Expected result

• The file has a part number in the registry, visible in GitMCloud and in GitM.
• The number becomes stamped into the actual file later, via GitM.

Troubleshooting

Symptom	Cause	Fix
Allocate action disabled	Your role is below Engineer.	Get write access.
Allocation failed after retries	Repeated registry conflicts.	Retry; ensure no one is mass-allocating simultaneously.
Number shows but file property is blank	It's allocated but not yet stamped (stamped: false).	Open the file in SolidWorks so GitM can stamp it.

Known limitations

• GitMCloud can allocate but never stamp. Stamping is SolidWorks-only.
• The registry schema, prefixes, and padding are a shared contract with GitM and must not be changed on one side only.