related: #325
This new GitHub Actions workflow listens for issue comments and processes commands to add or remove sub-issues using the Javascript client. It includes error handling and posts feedback to the issue for auditability as well as if any errors occur during execution.
Acceptable input formats (and multiple space-delimited arguments can be provided):
```
/add-sub-issue #1
/add-sub-issue 1
/add-sub-issue https://github.com/kubeflow/notebooks/issues/1
```
ℹ️ Be mindful of underlying constraints enforced in GH regarding sub-issues:
- An issue can only be a sub-issue to 0 or 1 issues
- Trying to add an issue as a sub-issue when it is already assigned as a sub-issue results in error
Also, in this commit, the ability to assign sub-issues is open to a set of users defined in the workflow yaml as a JSON string array within the job-level `if` conditional. The current collection identifies all epic owners and technical leaders for Notebooks 2.0.
Please note the workflow YAML file has been named generically to potentially house other "slash commands" in the future although the current implementation is only focused on `/add-sub-issue` and `/remove-sub-issue`.
Signed-off-by: Andy Stoneberg <astonebe@redhat.com>
* chore: create issue templates for project planning
related: #327
This commit creates 3 new GitHub issue templates to help with Notebooks 2.0 project planning.
As recently agreed upon in community meetings - we want to break down work into 3 hierarchical categories:
- Epics
- Features
- Tasks
The templates defined in this pull request mimic the format @ederign used when initially defining work
for our first "sprint" of work.
⚠️ Please note, however, I have introduced the term `Task` to capture the most granular issue type. Happy to change the word to something else - but wanted a `[...]` prefix to identify these issues similar to `[EPIC]` and `[FEATURE]`
These issue templates would not be intended to be used by "random" community members - rather they are designed to aid Epic Owners in defining work. For now, I have just added a simple "disclaimer" in the issue template summary to discourage use. In the future we could discuss extending `internal-acls` and leveraging GitHub Actions to ensure these "planning" templates are only used by designated community members.
The `Epic` and `Feature` templates **DO NOT** have a section to track child items included in the issue description. The desire to merge #325 to leverage GitHub sub-issues to more naturally track these relationships and avoid having to "ping" issue authors to update the description to track children.
The `config.yml` `issue_templates` section is used to define a deterministic order within the GitHub Template Chooser modal. As we can control the order through this file along - I also removed the leading numerical prefixes from existing yml template files as they serve no purpose and at worst could actively confuse.
Signed-off-by: Andy Stoneberg <astonebe@redhat.com>
* mathew: update epic label
Signed-off-by: Mathew Wicks <5735406+thesuperzapper@users.noreply.github.com>
* Update .github/ISSUE_TEMPLATE/planning_task.yml
Signed-off-by: Mathew Wicks <5735406+thesuperzapper@users.noreply.github.com>
* mathew: update feature label
Signed-off-by: Mathew Wicks <5735406+thesuperzapper@users.noreply.github.com>
* mathew: remove emoji from planning names
Signed-off-by: Mathew Wicks <5735406+thesuperzapper@users.noreply.github.com>
---------
Signed-off-by: Andy Stoneberg <astonebe@redhat.com>
Signed-off-by: Mathew Wicks <5735406+thesuperzapper@users.noreply.github.com>
Co-authored-by: Mathew Wicks <5735406+thesuperzapper@users.noreply.github.com>
* chore: Adding ADOPTERS.md file
Signed-off-by: Francisco Javier Arceo <farceo@redhat.com>
* fix typo from copy/paste
Signed-off-by: Francisco Javier Arceo <farceo@redhat.com>
* including openshift ai
Signed-off-by: Francisco Javier Arceo <farceo@redhat.com>
* Update ADOPTERS.md
Co-authored-by: Eder Ignatowicz <ignatowicz@gmail.com>
Signed-off-by: Francisco Arceo <farceo@redhat.com>
* Update ADOPTERS.md
Signed-off-by: Francisco Arceo <farceo@redhat.com>
---------
Signed-off-by: Francisco Javier Arceo <farceo@redhat.com>
Signed-off-by: Francisco Arceo <farceo@redhat.com>
Co-authored-by: Eder Ignatowicz <ignatowicz@gmail.com>
Andy Stoneberg
Andrey Velichkevich
Andy Stoneberg
Francisco Arceo
Mathew Wicks
Adem Baccara
James Liu