Radio buttons support

[14113]

I can see a great integration with checkboxes. Thanks for that!
Is it possible to add new support for Radio buttons?

The main motivation is a different context. On checkboxes, we want to finish all of them: https://docs.github.com/en/issues/tracking-your-work-with-issues/about-task-lists 4 of 6 tasks.

For radio buttons, we want to select only one option from the list.
For example, we are using issues like this:

**Describe the bug**
Blah blah

**Environment (please complete the following information):**
- [ ] Localhost
- [x] Staging
- [ ] Production

**Plan (please complete the following information):**
- [ ] PRO
- [x] Express
- [ ] Enterprise

We will never finish all tasks and can see on the issue index every time message: 2 of 6 tasks.

It's just an idea. Can imagine the complexity and another requests like select box, etc.

[denelon]

Similar discussion in #4319.

[ross-spencer]

Other connected issues: https://github.com/orgs/community/discussions/5238
And: https://github.com/orgs/community/discussions/5197

[JamesGelok]

It'd be nice if the syntax for radio buttons was something as easy as using parenthesis ( ) instead of square brackets [ ]

Hypothetically, your example would only need to be modified to use parenthesis instead.

**Describe the bug**
Blah blah

**Environment (please complete the following information):**
- ( ) Localhost
- (x) Staging
- ( ) Production

**Plan (please complete the following information):**
- ( ) PRO
- (x) Express
- ( ) Enterprise

I'm not sure how they model it. Maybe this would be something like "two tasks of a task list" where selecting any one of those radio buttons marks the completion of the task.

Can imagine the complexity and another requests like select box, etc.

Same, it'd be nice to answer questions like

What happens when you nest a radio list below a task list?

**Describe the bug**
Blah blah

**Environment (please complete the following information):**
- [ ] 
  - ( ) Localhost
  - (x) Staging
  - ( ) Production

**Plan (please complete the following information):**
- [ ] 
  - ( ) PRO
  - (x) Express
  - ( ) Enterprise

Maybe this would be something like "two tasks of a task list" where selecting any one of those radio buttons marks the completion of the task

This might just be a more explicit version of the above.

---

Can also imagine the other way around etc. And things with deeper nesting etc

[rafapaulin]

Interesting that almost three year later, there is no news on this basic feature :(

[kristymoniz-kubra]

yea, we were really hoping to introduce radio buttons for options so that users creating PRs can select from. Surprised this feature is still unavailable.

[JE29A]

I think radio groups need to be able to name the group they are part of, so incorporating some sort of id would be useful. [radio_id[ ]].

- [favorite_color[ ]] Red
- [favorite_color[x]] Green
- [favorite_color[ ]] Blue
- [favorite_shape[x]] Star
- [favorite_shape[ ]] Circle
- [favorite_shape[ ]] Square

Downside: Looks a lot like a text link: [Click here](http://somewhere.else/)

[rafapaulin]

double square brackets looks good to me :)

[logansease]

Ping! +1 Pretty pls consider :)

[Aierbote]

Another small feature related to this radio-button could be to mark an option as disable with this kind of syntax

- (/) = 🚫 
- (\) = 🚫 *Need to be sure the escape functinality doesn't kick in* 

[skyqrose]

In HTML, checked radio buttons can be disabled, too. So if GitHub made a syntax for disabling radio buttons, the syntax should probably also allow checked options to be disabled.

The current GitHub checkboxes don't support this syntax for disabled options (or being partially-checked. examples below). I think it would be enough for radio buttons to match the features that checkboxes have, which is just basic checked / unchecked states.

• unchecked
• checked
• [-] partial (doesn't work)
• [/] disabled (doesn't work)

[ShayokhShorfuddin]

Ping! Really hoping that we get checkbox support in 2025! 🙏

[udlose]

+1

[0xcaffeinated]

+1

[ShayokhShorfuddin]

+1. Let's make it happen.

[DIFSRIP]

+1

[ryangoree]

+1

[Keyurkariya]

+1

[bishiboosh]

Guys, please subscribe and/or add emoticons on the first message instead of sending unuseful comments.

[ryangoree]

[ShayokhShorfuddin]

Any development on this?

[marcellodesales]

Catching up with this once again, Dec 2nd, 2025... Wow, Github... listen to your customers...

[esafak]

It has been five years. It is safe to assume they are not interested in your money.

[Gruebes]

[dorianmariecom]

5 years

[colinemarie]

+1 🙏🏻 🤗