Description
Parse one Git attribute name and state token.
Git and diff tokens encode references, object metadata and patch coordinates. Parsing a local token does not resolve repository objects, establish identity or prove that a patch is complete or applicable.
Parse one Git attribute name and state token.
When to use this tool
Use Git Attribute Unset Vs Unspecified Token when inspecting the stated bounded Git or patch token.
How to use the tool and how it works
- Enter token. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read name, state. Use the output convention below.
Parse one Git attribute name and state token. Accept optional - or !, a restricted ASCII name and optional nonwhitespace =value; reject prefix-plus-value combinations and classify unset, unspecified, value or set.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| name | Name | Required. Text; maximum UTF-16 length 8192. |
| state | State | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"token": "-diff"
},
"output": {
"name": "diff",
"state": "unset"
}
}Limitations and assumptions
- The assigned value is not returned or applied; no attribute files are inspected.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Use Git itself against the intended repository for object resolution, complete validation, history interpretation or patch application.
References
Similar or alternative tools
- Git Path Spec Attribute State Token
Compare one pathspec attribute requirement with supplied attribute state.
- Git Ignore Negation Escape Pair
Distinguish leading ignore-pattern negation from escaped exclamation.