![]() Any additional context Command to run is npm test (not the wip) node.js. It seems I won’t be using my GitHub Graph API client, at least not for now, since the SQS message will contain the entire event, including all issue details. Setup a gitHub action to run tests after each commit. This means that with a single workflow, I can control on the AWS side how to react depending if action being taken in the issue ( opened, edited, closed, labeled, unlabeled…).Įventually I want to look into issue comments, but for that, I’ll probably define a separate workflow. You can use expressions to programmatically set environment variables in workflow files and access contexts. Adding the above works, but requires a change to the workflow build, rerun it, check the output, modify again to remove output again. After testing this new flow, sending the entire JSON payload to SQS, looks like contains the Activity Type. Contexts allow GitHub Actions to use our environment variables on any virtual machine, as these tasks aren’t always performed on the same virtual machine as we declare our environment. GitHub masks secrets when they are printed to the console, but you should be cautious when exporting or printing the context. ![]() It’s been a busy day, but now I’m back at it. Contexts, objects, and properties will vary significantly under different workflow run conditions. Each context is an object that contains properties, which can be strings or other objects. ![]() Still not sure if that will provide enough information to identify the Activity Type being performed in the issue. Contexts are a way to access information about workflow runs, variables, runner environments, jobs, and steps. OS: All Build Version: 20230518.5 Repro Steps: Click 'Focus Group' icon to focus the 'Function App' node.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |