Closed avidit closed 11 months ago
hi @avidit Sorry missed standup, can you explain whats' the difference between this approach and the legacy one developed by our team?
hi @avidit Sorry missed standup, can you explain whats' the difference between this approach and the legacy one developed by our team?
Are you referring to the Issues_workflow in the Dynamo repo? Here, I am just trying to automate transferring Dynamo issues filed here to Dynamo repo. And also use DynamoRevit Issues project for better management of issues.
hi @avidit Sorry missed standup, can you explain whats' the difference between this approach and the legacy one developed by our team?
Are you referring to the Issues_workflow in the Dynamo repo? Here, I am just trying to automate transferring Dynamo issues filed here to Dynamo repo. And also use DynamoRevit Issues project for better management of issues.
Understood, I saw another PR in Dynamo repo so I thought you are doing this both sides with some improvement
@Mikhinja Notice this PR does not affect regular code but only the Github Action automation we are using
Please Note:
DynamoRevit
repo will need to be cherry-picked into all the DynamoRevit Release branches that Dynamo supports. Contributors will be responsible for cherry-picking their reviewed commits to the other branches after aLGTM
label is added to the PR.Purpose
This will add workflow to automates issues added to the repo. The workflow will transfer Dynamo issues to Dynamo repo and move DynamoRevit issues through the appropriate columns in the project DynamoRevitIssues.
*Needs DYNAMOBOTTOKEN token as action secret for the repo
Declarations
Check these if you believe they are true
*.resx
filesReviewers
(FILL ME IN) Reviewer 1 (If possible, assign the Reviewer for the PR)
(FILL ME IN, optional) Any additional notes to reviewers or testers.
FYIs
(FILL ME IN, Optional) Names of anyone else you wish to be notified of