Why form validation does not work on private issue forms #148495
Replies: 3 comments
|
I ran into the same thing recently, and it's definitely frustrating. The required field only works for public repositories, which seems odd when you're working on private ones. From what I gather, it’s because private repos have stricter permissions and visibility settings. I get the reasoning, but it would be really helpful if GitHub made this feature available for private repos too. I’ve had to adjust my workflow around it, but it’s something I hope they’ll improve in the future. |
|
Good News: "required" is now working in Internal Repos! |
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Uh oh!
There was an error while loading. Please reload this page.
Select Topic Area
Question
Feature Area
Issues
Body
When opening a new issue in the repository, the required: true value does not work when we create a custom issue form in repositories that are Private.
It seems very illogical that this does not work in private repositories, is there a special reason?
Github Docs:
required (Boolean): If true, the form will not be submittable until this is filled out. Only for public repositories.
Guidelines
All reactions