Skip to content

feat(language-v2): track native Gemfile.lock from generator updates - #35030

Closed
torreypayne wants to merge 1 commit into
mainfrom
test-run-gapic-gitignore-lockfile
Closed

feat(language-v2): track native Gemfile.lock from generator updates#35030
torreypayne wants to merge 1 commit into
mainfrom
test-run-gapic-gitignore-lockfile

Conversation

@torreypayne

@torreypayne torreypayne commented Jul 28, 2026

Copy link
Copy Markdown
Member

This is a sample Draft PR to demonstrate and validate the generator changes introduced in gapic-generator-ruby#1320.

What this demonstrates:

  1. Un-ignoring the lockfile: Identifies that the .gitignore generated internally by gapic-generator-ruby across clients (e.g. google-cloud-language-v2) successfully omits Gemfile.lock.
  2. Organic lockfile generation: Validates that downstream processes (specifically the Dockerized Ruby Postprocessor orchestrated by OwlBot) successfully recognize the boundary, execute bundle lock within the standalone gem, and organically stamp a tracked, deterministic Gemfile.lock.

(DO NOT MERGE: This is purely a validation artifact.)

@torreypayne torreypayne added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Jul 28, 2026
@aandreassa

Copy link
Copy Markdown
Contributor

@torreypayne

  1. Please generate another random GAPIC just for testing.
  2. Are you running owlbot or new library? (this may be the reason for the copyright year diff).

],
"static": [
".OwlBot.yaml"
".OwlBot.yaml",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why does it add this? Is it a bug with .gitignore?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This seems like a new bug; there was a PR I approved/merged that addressed this same issue for a different gem: #35029

I'm not sure when this was introduced, but seems like we should file an issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Indicates a pull request not ready for merge, due to either quality or timing.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants