Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] [VDP] [Pipelines] Workflow automation #1022

Open
1 task done
chuang8511 opened this issue Jun 20, 2024 · 3 comments
Open
1 task done

[Feature] [VDP] [Pipelines] Workflow automation #1022

chuang8511 opened this issue Jun 20, 2024 · 3 comments
Labels
feature New feature or request Label need-triage Need to be investigated further

Comments

@chuang8511
Copy link
Member

Is There an Existing Issue for This?

  • I have searched the existing issues

Where do you intend to apply this feature?

Instill Core, Instill Cloud

Is your Proposal Related to a Problem?

Background

There are lots of project management tools now, and the internal information is scattered around in those tools.

Describe Your Proposed Solution

User stories

Story 1

As a project manager, he/she wants to align all information in all platform with correct format when a information is sync in one tool.

Possible pipelines
image

Concrete example
image

Highlight the Benefits

It can solve the problem in the real world.

Anything Else?

Possible components

  • Note: The sequence means the priority.

Application components

  • GitHub
  • Jira
  • Trello
  • Asana
  • Linear

Reference tools

  • I have not found the close product. We could imagine that the tools have been integrated AI solutions internally, such as Asana / Notion / Gmail /…
  • But, they do not have the process to sync the information to other ApplicationSource.
    • e.g. Asana information -> AI tools -> Linear / Slack / Gmail /…

Milestones

  1. Read the current pipelines
  1. Design the pipeline according to user stories.
  • Please draw the concrete pipelines first to ask us review before delving into development.
  • Timeline: 5 working days
  1. Check which components we are missing according to the designed pipeline.
  • Please create the skeleton PR first for the incoming components
  • Timeline: 2~3 working days
  1. Connect those components.
  • Timeline: 10 working days
  1. Build the designed pipeline after you connect those components.
  • Timeline: 1 working day

Note

  • About timeline, let's adjust it dynamically if there are much more complicated issues than we think
  • Milestone 2~5 is a cycle. Let's finish a whole complete user story first and then iterate it.
@chuang8511 chuang8511 added need-triage Need to be investigated further feature New feature or request labels Jun 20, 2024
Copy link

linear bot commented Jun 20, 2024

@github-project-automation github-project-automation bot moved this to 🚧 Planned in 🔮 Instill Core Jun 20, 2024
@YCK1130
Copy link

YCK1130 commented Jun 24, 2024

Hi @chuang8511 ! As shown in the following figure, I plan to construct a pipeline to assist the code review process.
Screenshot 2024-06-24 at 2 16 25 PM
I would appreciate any feedback!

TODO - Add a GitHub component

Must

  • read a pull request data
  • read commit messages
  • comment under a pull request
  • register webhook

Additional

  • Post issue
  • Create pull request
  • Edit pull request
  • Edit issue

@chuang8511
Copy link
Member Author

chuang8511 commented Jun 24, 2024

Hi @YCK1130 cc'd mentor(@xiaofei-du ) Project Lead (@donch1989 )
Thanks for providing this clear image.

There are a few things we need to do and check before delving into development.

  1. TODO: I forgot to add the user story about your GitHub story. Could you help me write it in this ticket or your sub-ticket?

    • e.g. As a engineer manager, he/she wants to ....
  2. Feedback: I am not a proficient in this domain, but, in my opinion, current design looks similar with lint function such as golintci.

    • I guess we need to input more data rather than only PR information. When I review others' code, I also read the code that is not in the PR files. So, it means LLM model probably requires those information to provide a good result.
  3. Feedback: Previously, I had to review others' code. Usually, I only review function code rather than test code. I think it would be good that there is a system to help me review the quality of test code.

    • e.g. test coverage / mock strategy / ...

Please feel free to comment back if there is anything unclear.

donch1989 added a commit to instill-ai/component that referenced this issue Jul 28, 2024
Because

- We need a Jira component to complete some development automation tasks
- Related Issue: instill-ai/instill-core#1022

This commit

- Support get boards/issue/epic/sprint

TODO
- [x] TASK_LIST_BOARDS: list all boards in Jira
- [x] TASK_LIST_ISSUES: list issues in Jira by various methods
- [x] TASK_GET_ISSUE: get an issue by ID or key
- Note: This API can get issue/epic with the key since they use the same
indexing system.
- [x] TASK_GET_SPRINT: get a sprint by ID

Next PR
- create issue
- create epic
- create sprint

Added by @chuang8511 to visualise Jira's design

![image](https://github.com/user-attachments/assets/17ff0aaf-5ab0-458c-95cd-a147f12e314a)

---------

Co-authored-by: Chang, Hui-Tang <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request Label need-triage Need to be investigated further
Projects
No open projects
Status: 🚧 Planned
Development

No branches or pull requests

3 participants