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.

Sign up for GitHub

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

Jump to bottom

[REVIEW] Auto-add new Issues and PRs to cuspatial's project #618

Merged
merged 2 commits into from
Oct 4, 2022
Merged

[REVIEW] Auto-add new Issues and PRs to cuspatial's project #618

merged 2 commits into from
Oct 4, 2022

Conversation

jarmak-nv
Copy link
Contributor

The new project boards should have every issue/PR within them. This workflow makes the addition of the issues/PRs automatic rather than the current manual process.

@jarmak-nv
Auto-add new Issues and PRs to cuspatial's project
ac27346 
The new project boards should have every issue/PR within them. This workflow makes the addition of the issues/PRs automatic rather than the current manual process.
@jarmak-nv jarmak-nv added 3 - Ready for Review Ready for review by team feature request New feature or request labels Aug 2, 2022
@jarmak-nv jarmak-nv requested a review from a team as a code owner August 2, 2022 15:23
@jarmak-nv jarmak-nv added the non-breaking Non-breaking change label Aug 2, 2022
@jarmak-nv jarmak-nv requested review from a team, zhangjianting and jrhemstad and removed request for a team August 2, 2022 15:33
thomcom
thomcom approved these changes Aug 2, 2022
View reviewed changes
Copy link
Contributor

@thomcom thomcom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

harrism
harrism approved these changes Aug 2, 2022
View reviewed changes
Copy link
Member

@harrism harrism left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Neat!

@jarmak-nv
Copy link
Contributor Author

For viz: we need to create a new org secret that has the required access, the workflow fails using the existing secret so until we get that settled this will sit.

@harrism
Copy link
Member

harrism commented Aug 3, 2022

@jarmak-nv can you retarget this to 22.10? We missed the boat for 22.08.

@jarmak-nv
Copy link
Contributor Author

@harrism yeah I'll update the target once the new key is created and I can update that at the same time. This will probably be sitting until after 22.08 gets fully released.

@thomcom thomcom changed the base branch from branch-22.08 to branch-22.10 August 4, 2022 14:42
@thomcom
Copy link
Contributor

thomcom commented Aug 4, 2022

I went ahead and changed the base.

@harrism
Copy link
Member

harrism commented Aug 4, 2022

@jarmak-nv you will need to merge 22.10 into your branch and push in order to complete the move to 22.10.

@harrism
Copy link
Member

harrism commented Aug 24, 2022

@jarmak-nv what's happening with this?

@github-actions
Copy link

This PR has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this PR if it is no longer required. Otherwise, please respond with a comment indicating any updates. This PR will be labeled inactive-90d if there is no activity in the next 60 days.

@jarmak-nv jarmak-nv requested a review from harrism October 3, 2022 20:08
@harrism
Copy link
Member

harrism commented Oct 4, 2022

@gpucibot merge

msadang
msadang approved these changes Oct 4, 2022
View reviewed changes
Copy link
Contributor

@msadang msadang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

@rapids-bot rapids-bot bot merged commit 0e0c7f3 into branch-22.10 Oct 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@raydouglass raydouglass raydouglass left review comments

@msadang msadang msadang approved these changes

@harrism harrism harrism approved these changes

@thomcom thomcom thomcom approved these changes

@zhangjianting zhangjianting Awaiting requested review from zhangjianting zhangjianting was automatically assigned from rapidsai/cuspatial-cpp-codeowners

@jrhemstad jrhemstad Awaiting requested review from jrhemstad jrhemstad was automatically assigned from rapidsai/cuspatial-cpp-codeowners

Assignees
No one assigned
Labels
3 - Ready for Review Ready for review by team feature request New feature or request non-breaking Non-breaking change
Projects
cuSpatial
Status: Done
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@jarmak-nv @harrism @thomcom @raydouglass @msadang