A team wants their published custom action to display a recognisable icon and colour on its GitHub Marketplace listing. They are editing the branding section of action.yml and need to know which two keys that section accepts and the constraint on their values. Which statement about the branding keys is correct?
- Abranding accepts icon and color, where icon must be the name of a supported Feather icon and color must be one of the named colours from the allowed palette. Correct
- Bbranding accepts logo and background, where logo is any uploaded PNG file path and background is a hex colour code applied behind the action's listing card.
- Cbranding accepts icon and theme, where icon is a Feather icon name and theme selects a light or dark presentation for the action's Marketplace card.
- Dbranding accepts image and color, where image is a URL pointing to a hosted icon and color is a free-form hex value that styles the listing border.
Why A is correct: The branding block defines exactly icon and color, with icon set to a supported Feather icon name and color restricted to a fixed list of named colours, which matches the documented constraint.
Why B is wrong: Tempting because real listings show an image and a colour, but the keys are icon and color, the icon is a named Feather icon not an uploaded file, and there is no background key.
Why C is wrong: Tempting since icon is genuinely valid, but the second key is color drawn from a fixed palette, not a theme selector, so a light or dark theme value is not recognised.
Why D is wrong: Tempting because color is half right, but the first key is icon naming a built-in icon rather than an image URL, and color must come from a named set rather than an arbitrary hex value.