fix test

[Lokowitz]

Community Contribution License Agreement

By creating this pull request, I grant the project maintainers an unlimited,
perpetual license to use, modify, and redistribute these contributions under any terms they
choose, including both the AGPLv3 and the Fossorial Commercial license terms. I
represent that I have the right to grant this license for all contributed content.

Description

How to test?

[gemini-code-assist]

Summary of Changes

Hello @Lokowitz, I'm Gemini Code Assist¹! 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 introduces a new dev-build target in the Makefile. This addition aims to streamline the development workflow by providing a convenient command to build and tag the project's Docker image locally. While the PR title suggests a test fix, the actual change focuses on enhancing the build process, which could indirectly support testing efforts by providing an updated development environment.

Highlights

• New Makefile Target: A new dev-build target has been added to the Makefile.
• Docker Image Build: This new target automates the process of building a Docker image for the project, tagging it as fosrl/olm:latest.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/test.yml

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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

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. ↩

[gemini-code-assist]

Code Review

This pull request introduces a new dev-build target in the Makefile to facilitate building a local development Docker image. My review focuses on improving this new target. I've suggested marking the target as .PHONY in line with Makefile best practices and changing the Docker tag from :latest to :dev to prevent potential conflicts with release builds. These adjustments will enhance the reliability and clarity of the development process.

[gemini-code-assist]

This new target dev-build should be declared as .PHONY. This is a Makefile best practice to prevent conflicts with a file of the same name and to indicate that the target doesn't produce an output file with that name. You can add dev-build to an existing .PHONY declaration at the top of the file.

[gemini-code-assist]

Using the :latest tag for a development build can cause conflicts with the docker-build-release target, which also tags the image as :latest. This can lead to confusion or accidentally using a local development image instead of a production-ready one. It's recommended to use a specific tag for development, such as :dev.

	docker build -t fosrl/olm:dev .