Skip to content

Conversation

@davidcavazos
Copy link

Description

Checklist

  • I have followed guidelines from CONTRIBUTING.MD and Samples Style Guide
  • Tests pass: npm test (see Testing)
  • Lint pass: npm run lint (see Style)
  • These samples need a new API enabled in testing projects to pass (let us know which ones)
  • These samples need a new/updated env vars in testing projects set to pass (let us know which ones)
  • This pull request is from a branch created directly off of GoogleCloudPlatform/nodejs-docs-samples. Not a fork.
  • This sample adds a new sample directory, and I updated the CODEOWNERS file with the codeowners for this sample
  • This sample adds a new sample directory, and I created GitHub Actions workflow for this sample
  • This sample adds a new Product API, and I updated the Blunderbuss issue/PR auto-assigner with the codeowners for this sample
  • Please merge this PR for me once it is approved

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Hello @davidcavazos, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

This pull request aims to add id-token to workflows. Since the provided context lacks specific file changes, I'm unable to provide a detailed breakdown of the modifications. However, based on the title, the intent is to enhance the security or authentication process within the workflows by incorporating id-token functionality.

Highlights

  • Feature Enhancement: The primary goal is to integrate id-token into existing workflows.
  • Security: The addition of id-token likely aims to improve the security posture of the workflows.

Changelog

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


A token's flight,
Secures the workflow's might,
Safe passage it brings.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@product-auto-label product-auto-label bot added samples Issues that are directly related to samples. api: workflows Issues related to the Workflows API. labels Apr 4, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

The pull request aims to add id-token to workflows. The changes seem straightforward and necessary for enhanced security and authentication. I have reviewed the changes and provided feedback where improvements can be made.

Merge Readiness

The pull request appears to be in good shape for merging, but I recommend addressing the identified issues before merging. I am unable to directly approve the pull request, and others should review and approve this code before merging.

@davidcavazos davidcavazos marked this pull request as ready for review April 4, 2025 20:30
@davidcavazos davidcavazos requested review from a team as code owners April 4, 2025 20:30
@davidcavazos davidcavazos merged commit 63bc5f0 into main Apr 4, 2025
14 checks passed
@davidcavazos davidcavazos deleted the support-forks branch April 4, 2025 20:31
rudrakhsha-crest pushed a commit to rudrakhsha-crest/nodejs-docs-samples that referenced this pull request Apr 18, 2025
* feat: support testing on forked repos

* add pull_request to test on PR

* remove prod suffix

* decode json on matrix paths

* add experimental to check names

* add experimental to job names

* run test only if paths is not empty

* test explicitly against empty array

* move experimental as a prefix

* success check if no paths are found

* always set check to done

* remove pull_request trigger

* rearrange if check

* add more comments

* fix: add id-token to workflows
rudrakhsha-crest added a commit to rudrakhsha-crest/nodejs-docs-samples that referenced this pull request Apr 18, 2025
* feat: support testing on forked repos

* add pull_request to test on PR

* remove prod suffix

* decode json on matrix paths

* add experimental to check names

* add experimental to job names

* run test only if paths is not empty

* test explicitly against empty array

* move experimental as a prefix

* success check if no paths are found

* always set check to done

* remove pull_request trigger

* rearrange if check

* add more comments

* fix: add id-token to workflows
rudrakhsha-crest added a commit to rudrakhsha-crest/nodejs-docs-samples that referenced this pull request Apr 18, 2025
* feat: support testing on forked repos

* add pull_request to test on PR

* remove prod suffix

* decode json on matrix paths

* add experimental to check names

* add experimental to job names

* run test only if paths is not empty

* test explicitly against empty array

* move experimental as a prefix

* success check if no paths are found

* always set check to done

* remove pull_request trigger

* rearrange if check

* add more comments

* fix: add id-token to workflows
rudrakhsha-crest added a commit to rudrakhsha-crest/nodejs-docs-samples that referenced this pull request Apr 18, 2025
* feat: support testing on forked repos

* add pull_request to test on PR

* remove prod suffix

* decode json on matrix paths

* add experimental to check names

* add experimental to job names

* run test only if paths is not empty

* test explicitly against empty array

* move experimental as a prefix

* success check if no paths are found

* always set check to done

* remove pull_request trigger

* rearrange if check

* add more comments

* fix: add id-token to workflows
rudrakhsha-crest pushed a commit to rudrakhsha-crest/nodejs-docs-samples that referenced this pull request Apr 18, 2025
* feat: support testing on forked repos

* add pull_request to test on PR

* remove prod suffix

* decode json on matrix paths

* add experimental to check names

* add experimental to job names

* run test only if paths is not empty

* test explicitly against empty array

* move experimental as a prefix

* success check if no paths are found

* always set check to done

* remove pull_request trigger

* rearrange if check

* add more comments

* fix: add id-token to workflows
utsav1810 pushed a commit that referenced this pull request May 19, 2025
* Added CRUD code snippets with codeowners file

* Solved linting errors

* Added sanitization code snippets along with test cases

* Added header comment

* Removed hardcoded value from test file

* Removed crud related files

* Addressed gemini bot comments

* Updated prompts, tests and log statements for sanitization APIs

* chore(cloud-sql): migrate mysql, postgres samples to new CI (#4055)

* chore(cloud-sql): migrate mysql, postgres samples to new CI

* rename to match postgres version

* acquireTimeout warns in mysql2, remove

* mysql2 query returns [results, fields], so only return fields

* remove unused test scripts

* revert bot-suggested rename: would cause excessive region tag change

* chore(compute): Migrate region tag (#4047)

* chore(compute): Migrate region tag

* chore(compute): Rename region tag

* chore(compute): Renove older region tag (#4062)

overriding failure as this is jsut removing the region tag.

* feat: support testing on forked repos (#4057)

* feat: support testing on forked repos

* add pull_request to test on PR

* remove prod suffix

* decode json on matrix paths

* add experimental to check names

* add experimental to job names

* run test only if paths is not empty

* test explicitly against empty array

* move experimental as a prefix

* success check if no paths are found

* always set check to done

* remove pull_request trigger

* rearrange if check

* add more comments

* fix: add id-token to workflows (#4063)

* feat: support testing on forked repos

* add pull_request to test on PR

* remove prod suffix

* decode json on matrix paths

* add experimental to check names

* add experimental to job names

* run test only if paths is not empty

* test explicitly against empty array

* move experimental as a prefix

* success check if no paths are found

* always set check to done

* remove pull_request trigger

* rearrange if check

* add more comments

* fix: add id-token to workflows

* chore: update the minimum language based on maintenance mode

* chore(deps): pin dependencies (#4035)

* Added region tags to snippets

* Updated region tags for code snippets based on errors

* Removed extra csam assertions in sanitization tests

* Addressed review comments

* Updated test cases for sanitization snippets, added test for rai filter

* Updated tests as per review comments

* updated commented variables sample values in code snippets

* Addressed review comments and updated tests accordingly

* removed-todo-developer-comments

* add-new-line-eslintrc

* fix-linting-warnings-and-errors

* fixed-tests

* revert-security-center-change

* revert-security-center-change

* revert-security-center-change

* fix-minor-lint

---------

Co-authored-by: Eric Schmidt <[email protected]>
Co-authored-by: Harsh Nasit <[email protected]>
Co-authored-by: harshnasitcrest <[email protected]>
Co-authored-by: David Cavazos <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: workflows Issues related to the Workflows API. samples Issues that are directly related to samples.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants