Privacy Policy Banner

We use cookies to improve your experience. By continuing, you agree to our Privacy Policy.

What to know about the launch of “sub-stands” by GitHub

What to know about the launch of “sub-stands” by GitHub
What to know about the launch of “sub-stands” by GitHub

Github has just launched a novelty which should delight developers who juggle with complex projects: sub-issues (Subtaches). This feature, still being deployed, makes it possible to structure the tasks more clearly in a way out, by breaking them down into hierarchical subtaches. Clearly: better organization, without getting out of your issue principal.

Why did GitHub add this functionality?

For a long time, the issues are at the heart of project management on Github. With increasingly complex projects, the demand for a native system to supervise dependencies and the hierarchy between tasks became pressing. With the sub-stands, we can now Create a structured subtacked list directly inside a way out. Each sub -issue is a real full-fledged outcome, with its own number, its own condition, and can be linked to another repo. Practical for monitoring between deposits or for large -scale projects.

How to translate “sub-stand” into ?

The term has no perfect equivalent in French, but we can talk about subtachesor more precisely sous-issues If we stay in the GitHub context. These are nested outcomes, which appear directly in a main outcome and make it possible to cut a complex task into simpler steps, while keeping an overview of the work to be accomplished.

What it changes in practice

The goal is clear: to help you Organize your exits as detailed action planswithout multiplying the tickets or losing the thread of the outbuildings.
For example :

  • An outcome for feature can include all the necessary steps (IU, Backend, Tests) in the form of sub -issues.

  • Each sub -issue can then be associated with a dedicated PR.

  • The system automatically follows the progression: checking an underside, the overall progression is acting.

All this natively integrates into the Github interface, with a Fluid navigationresearch filters like has:sub-issues-progressand a management designed for teams.

A functionality thought for the devs … by devs

Github has actively tested the sub-stands internally, using them to … build the sub-stands. This use in “dogfooding” made it possible to optimize ergonomics, to adapt the metadata displayed (for example, the name of the repo of a linked sub -issue) and to build a system which remains faithful to the simplicity of use specific to Github.

Accessible via the interface but also via GraphQLthe functionality is based on a Optimized data architecture And fits perfectly with the Github Enterprise Server and Cloud tools.

If you are an source contributor, maintaining or simply regular user of GitHub, Test the sub-stands As soon as they are available on your deposits.

I like that:

I like loading…

-

PREV The Socan responds to the concerns of music publishers as part of two meetings
NEXT Rania Toukebri, a Tunisian engineer at the heart of the Lunar Mission Artemis II of NASA!