Requesting a Change

Do you have an idea that could make Go Advanced Admin better? Whether it is a new feature, an improvement to an integration, or a tweak to our tooling, this page explains how to propose changes.

Check for Existing Discussions

• Browse open issues and discussions to see if someone has already suggested a similar change.
• Comment on an existing thread instead of opening a new one to keep related conversation in one place.

When to Use Issues vs. Discussions

• GitHub Discussions: Ideal for brainstorming, high-level ideas, and questions about feasibility. Start here if you want feedback before committing to an implementation.
• GitHub Issues: Use issues when you are ready to request or work on a specific change. Provide as many actionable details as possible to help maintainers evaluate the request.

Filing a Feature Request Issue

1. Open the feature request template.
2. Describe the problem you are trying to solve and why it matters.
3. Outline the solution you are proposing. Include examples, pseudo code, or UI sketches if relevant.
4. Share any alternatives you considered and why they may not work.
5. Submit the issue and monitor responses so the conversation can move forward quickly.

Collaborate on the Proposal

• Be open to feedback—maintainers might suggest adjustments to align with project goals.
• If you plan to implement the change, mention it in the issue so others know it is in progress.
• Update the issue as you make progress or if your plans change.

Clear, detailed requests help us understand priorities and shape the roadmap together.