Skip to content

Conversation

hpractv
Copy link
Contributor

@hpractv hpractv commented Sep 5, 2024

Summary of PR changes

PR Requirements

  • For major, minor, or breaking changes, at least one of the commit messages contains the appropriate +semver: keywords.
    • See the Incrementing the Version section of the repository's README.md for more details.
  • The action code does not contain sensitive information.

NOTE: If the repo's workflow could not automatically update the README.md, it should be updated manually with the next version. For javascript actions, if the repo's workflow could not automatically recompile the action it should also be updated manually as part of the PR.

@hpractv hpractv requested a review from a team as a code owner September 5, 2024 17:17
@hpractv hpractv changed the title - Added deployment unit and integration testing Added deployment unit and integration testing Sep 5, 2024
Copy link

github-actions bot commented Sep 5, 2024

Jest Results

Generic badge

Duration: 1.392 seconds
Start: 2024-09-05 14:22:32.126 MDT
Finish: 2024-09-05 14:22:33.518 MDT
Duration: 1.392 seconds
Outcome: Passed | Total Tests: 11 | Passed: 11 | Failed: 0
Total Test Suites: 2
Total Tests: 11
Failed Test Suites: 0
Failed Tests: 0
Passed Test Suites: 2
Passed Tests: 11

Copy link

github-actions bot commented Sep 5, 2024

Before this PR can be merged, the following item(s) should be addressed to comply with the action's Contributing Guidelines.

  • Please ensure the action has been recompiled by running the following command from the root of the repository:
    npm run build

Copy link

github-actions bot commented Sep 5, 2024

The action's Contributing Guidelines have been met:

  • The action's version in the Usage Examples section of README.md has been updated to @v1.0.8
  • The action has been recompiled (if needed) by running the build command from the root of the repository

Copy link

github-actions bot commented Sep 5, 2024

Before this PR can be merged, the following item(s) should be addressed to comply with the action's Contributing Guidelines.

  • Please ensure the action has been recompiled by running the following command from the root of the repository:
    npm run build

Copy link

github-actions bot commented Sep 5, 2024

The action's Contributing Guidelines have been met:

  • The action's version in the Usage Examples section of README.md has been updated to @v1.0.8
  • The action has been recompiled (if needed) by running the build command from the root of the repository

Comment on lines +14 to +16
const createOctokitClient = token => new Octokit({ auth: token });
const createOctokitGraphQLClient = token =>
graphql.defaults({ headers: { authorization: `token ${token}` } });

Choose a reason for hiding this comment

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

Is there an advantage to defining a function that creates an octokit client as opposed to creating a single client that is passed to the functions that need it? It seems like having a single client that all the different functions use might be better than each function creating its own version of the client.

Copy link
Contributor Author

@hpractv hpractv Sep 5, 2024

Choose a reason for hiding this comment

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

This function is getting used by the deployment testing file, too. I wanted to make sure the setting params for these clients were the same in both the runtime code as well as the jest test.

status => {
process.env[inputKey('deployment-status')] = status;
try {
const testConext = setup();

Choose a reason for hiding this comment

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

This is a nitpick but it looks like there is a typo here. testConext => testContext.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

👍🏽

Copy link

github-actions bot commented Sep 5, 2024

The action's Contributing Guidelines have been met:

  • The action's version in the Usage Examples section of README.md has been updated to @v1.0.8
  • The action has been recompiled (if needed) by running the build command from the root of the repository

Copy link

github-actions bot commented Sep 5, 2024

The action's Contributing Guidelines have been met:

  • The action's version in the Usage Examples section of README.md has been updated to @v1.0.8
  • The action has been recompiled (if needed) by running the build command from the root of the repository

@hpractv hpractv merged commit 8bbb82b into main Sep 5, 2024
4 checks passed
@hpractv hpractv deleted the graphql-node-count branch September 5, 2024 20:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants