ProjectsV2: Manage Project Views via GraphQL

[pyoio]

Select Topic Area

Question

Feature Area

Projects

Body

Hi, the GraphQL API has all the required machinery to manage ProjectV2 fields (<create|update|delete>ProjectV2Field()), it would be incredibly useful to be able to do the same to manage views, we have a couple of motivating use cases:

1. Be able to define project fields and views in code in a repo, and automatically apply them to one or more projects
2. Be able to keep multiple projects in sync with a template project that has been updated since the child project was copied

A suitable alternative would be that GitHub automate some way for child projects to have fields and views auto-synced to the template project they spawned from, with some level of configurability (e.g., the ability to exempt specific fields from having their field values sync'd)

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[oleg-proudnikov]

This makes a lot of sense. It would be great if GitHub reconciled template to all child projects. Perhaps this inheritance would be on an opt-in basis. Alternatively a child project could have an Sync Fields/Views from Template. However, it looks like the decision to decouple a Project from its template is intentional due to complexity of this relationship.

Having an API would make sense here. If I could create a set of Views in a template and then copy them via an API to several projects, it would achieve the same outcome.