Conversation
|
We should also redo the rest of the elements as well |
Summary of ChangesHello, 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! This pull request significantly refactors the build system for 1Password and 1Password CLI by centralizing architecture-specific configurations. Instead of maintaining separate files for Highlights
Changelog
Activity
Using Gemini Code AssistThe 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 by creating a comment using either
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 Limitations & Feedback Gemini Code Assist 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. 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. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request refactors the BuildStream elements for 1password and 1password-cli. It consolidates previously separate architecture-specific and common definition files (e.g., 1password-cli-x86_64.bst, 1password-cli-aarch64.bst, and 1password-cli.inc) into single, top-level elements/bluefin/1password-cli.bst and elements/bluefin/1password.bst files. These new files now use BuildStream's conditional logic to handle architecture-specific sources and configurations. The elements/bluefin/deps.bst file is updated to reflect these simplified element paths.
4230d90 to
694b1bf
Compare
The only different part was the per-arch specific sources, but suing the
following yaml syntax we can put the conditional inline the file.
```yaml
sources:
- kind: tar
(?):
- arch == "x86_64":
url: foo
ref: foo
- arch == "aarch64":
url: bar
ref: bar
```
694b1bf to
41a05f6
Compare
The only different part was the per-arch specific sources, but suing the following yaml syntax we can put the conditional inline the file.