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

CI operation that create VATZ weekly meeting #417

Closed
xellos00 opened this issue Mar 18, 2023 · 23 comments
Closed

CI operation that create VATZ weekly meeting #417

xellos00 opened this issue Mar 18, 2023 · 23 comments
Assignees
Labels
area:ci/cd Anything related to build or update CI/ CD process. type: bi-weekly sync issue that must be shared during bi-weekly sync meeting Vatz Project Name

Comments

@xellos00
Copy link
Member

xellos00 commented Mar 18, 2023

What does it require to on Vatz

A clear and concise description of what you expected to happen through Ci/CD

No automatic register process VATZ weekly sync on discussion per bi-weekly.

Expected behavior

A clear and concise description of results after CI/CD implementation.

Create a new General discussion every two weeks automatically.

  1. Register new milestone that includes

    • #number of milestone
    • Due date on milestone.
  2. Include Screenshot if possible.

  3. Add template on that.

How to run

Please, Update and give simple guide to run CI/CD process with this issue.

No action requires to run discussion.

Screenshots

If applicable, add screenshots to help explain your problem

@xellos00 xellos00 added Vatz Project Name area:ci/cd Anything related to build or update CI/ CD process. labels Mar 18, 2023
@xellos00 xellos00 self-assigned this Mar 18, 2023
@xellos00 xellos00 added the type: bi-weekly sync issue that must be shared during bi-weekly sync meeting label Mar 18, 2023
@xellos00
Copy link
Member Author

xellos00 commented May 9, 2023

@gnongs
Can you handle this issue as you did on Validator?

@xellos00 xellos00 assigned gnongs and unassigned xellos00 May 9, 2023
@gnongs
Copy link
Member

gnongs commented May 9, 2023

@gnongs Can you handle this issue as you did on Validator?

Okay. I will try it!

@gnongs
Copy link
Member

gnongs commented May 10, 2023

Test repository: https://github.com/gnongs/create-discussion

Currently proceed to testing.

@gnongs
Copy link
Member

gnongs commented May 10, 2023

Obtain repository-id and category-id

Link: https://docs.github.com/en/graphql/overview/explorer

query MyQuery {
  repository(name: "<REPO_NAME>", owner: "<REPO_OWNER>") {
    id
    discussionCategories(first: 10) {
      edges {
        node {
          id
          name
        }
        cursor
      }
    }
  }
}

@gnongs
Copy link
Member

gnongs commented May 10, 2023

$ gh workflow run create-discussion.yml
$ gh run list --workflow=create-milestone.yml

@gnongs
Copy link
Member

gnongs commented May 10, 2023

@gnongs
Copy link
Member

gnongs commented May 10, 2023

  • What is template?
  • What time do you want to create a discussion & milestone?
  • Should I close the previous milestone?

@xellos00
Copy link
Member Author

@gnongs

  • What is template?
  • What time do you want to create a discussion & milestone? UTC
  • Should I close the previous milestone? You don't have to
    Please create one, when VATZ bi-weekly meeting is over.

@gnongs
Copy link
Member

gnongs commented May 11, 2023

@xellos00
Currently, making Discussion and creating Milestone githubaction are ready.

Action link: https://github.com/gnongs/create-discussion/actions/runs/4946512567

image image

If you answer the above, I think we can finish the issue by correcting it accordingly :)

@gnongs
Copy link
Member

gnongs commented May 15, 2023

Before we apply

We need to set below value on repository.

  1. Go to https://docs.github.com/ko/graphql/overview/explorer
  2. Run below query
query MyQuery {
  repository(name: "vatz", owner: "dsrvlabs") {
    id
    discussionCategories(first: 10) {
      edges {
        node {
          id
          name
        }
        cursor
      }
    }
  }
}
  1. Set value on repository secret
DISCUSSION_REPO_ID= #data.repository.id
DISCUSSION_CATE_ID= #data.repository.discussionCategories.edges[1].node.id

@xellos00 Could you proceed above steps? If you don't understand something, please feel free to ask.

@xellos00
Copy link
Member Author

Before we apply

We need to set below value on repository.

  1. Go to https://docs.github.com/ko/graphql/overview/explorer
  2. Run below query
query MyQuery {
  repository(name: "vatz", owner: "dsrvlabs") {
    id
    discussionCategories(first: 10) {
      edges {
        node {
          id
          name
        }
        cursor
      }
    }
  }
}
  1. Set value on repository secret
DISCUSSION_REPO_ID= #data.repository.id
DISCUSSION_CATE_ID= #data.repository.discussionCategories.edges[1].node.id

@xellos00 Could you proceed above steps? If you don't understand something, please feel free to ask.

@xellos00
Can you give me a call when you are available for this week?
let's go over together and check its working status together.

@xellos00 xellos00 added this to the Sprint 34 ( ~ 2023-05-24) milestone May 18, 2023
@gnongs
Copy link
Member

gnongs commented May 18, 2023

@xellos00 Can you give me a call when you are available for this week? let's go over together and check its working status together.

@xellos00 Then how about at 2023-05-19T10:00:00+09:00:00?

@xellos00
Copy link
Member Author

name: Add Label to Discussion

on:
  issues:
    types:
      - opened

jobs:
  add-label:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/github/get-discussion@v1
        with:
          issue_number: ${{ github.event.issue.number }}

      - uses: actions/github/list-labels@v1
        with:
          discussion_id: ${{ steps.get-discussion.outputs.discussion_id }}

      - uses: actions/github/add-label@v1
        with:
          label: ${{ steps.list-labels.outputs.labels[0] }}
          discussion_id: ${{ steps.get-discussion.outputs.discussion_id }}

@xellos00
Copy link
Member Author

xellos00 commented May 19, 2023

Before we apply

We need to set below value on repository.

  1. Go to https://docs.github.com/ko/graphql/overview/explorer
  2. Run below query
query MyQuery {
  repository(name: "vatz", owner: "dsrvlabs") {
    id
    discussionCategories(first: 10) {
      edges {
        node {
          id
          name
        }
        cursor
      }
    }
  }
}
  1. Set value on repository secret
DISCUSSION_REPO_ID= #data.repository.id
DISCUSSION_CATE_ID= #data.repository.discussionCategories.edges[1].node.id

@xellos00 Could you proceed above steps? If you don't understand something, please feel free to ask.

I've added those following secrets for actions.
image

@xellos00
Copy link
Member Author

xellos00 commented May 19, 2023

@gnongs
I approve and merged PR

Can you continue test on VATZ?
Please, let me know if you do not have auth.

@xellos00 xellos00 linked a pull request May 19, 2023 that will close this issue
4 tasks
@gnongs
Copy link
Member

gnongs commented May 22, 2023

@xellos00 First, there were some issues with the github token, so I fixed that (d8dd435)

And I tested two things.

  1. Test was to see if it wouldn't run unless it was on a specified date, and it worked fine.(https://github.com/dsrvlabs/vatz/actions/runs/5043073042)

  2. I checked to see if it would run on the specified date, and it did.

Please check the above, and if everything looks good, I'll create the final PR and delete test discussion and milestone.

@gnongs
Copy link
Member

gnongs commented May 22, 2023

@xellos00 I've looked for a way to set the label on the discussion, but I don't think there's a way to do that. Can I ask you to check?

  • Check ChatGPT
    image

@xellos00
Copy link
Member Author

@gnongs
Can you test this on current repo? and then
give me a discussion list that you've created while you test it.
I will delete them when you finish the test.

@gnongs
Copy link
Member

gnongs commented May 23, 2023

@xellos00
This repository has only been tested once (because multiple meaningless things are created) and the corresponding discussion and milestone are as follows. As I wrote above, I think it's enough!

@xellos00
Copy link
Member Author

xellos00 commented May 24, 2023

@xellos00 This repository has only been tested once (because multiple meaningless things are created) and the corresponding discussion and milestone are as follows. As I wrote above, I think it's enough!

Cool. It's all good.
I will leave a discussion as it is for you to test add labels

@xellos00
Copy link
Member Author

No label available for discussion for now.
let's do it together!!

@xellos00
Copy link
Member Author

@gnongs
As final confirmation, I am going to close this issue unless there is further step additional features in development.
Can you confirm and close this issue?
let me know if there's any comment for this issue.

@gnongs
Copy link
Member

gnongs commented Aug 11, 2023

When I checked CI about creating discussion and milestone, it is working well.

So I will close this issue.

@gnongs gnongs closed this as completed Aug 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:ci/cd Anything related to build or update CI/ CD process. type: bi-weekly sync issue that must be shared during bi-weekly sync meeting Vatz Project Name
Projects
None yet
Development

No branches or pull requests

2 participants