Add example of setting commit statuses on Forgejo

[betulependule]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @betulependule, 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 valuable new example that illustrates how to automate the setting of commit statuses on Forgejo using the ogr library. This functionality is crucial for integrating custom CI/CD pipelines or external tools that need to report build or test results directly onto pull requests, thereby enhancing the automation capabilities and feedback loop for developers working with Forgejo.

Highlights

• New Example Notebook: A new Jupyter Notebook, set_commit_status.ipynb, has been added to the examples directory. This notebook demonstrates how to programmatically set commit statuses on Forgejo instances.
• Forgejo Integration: The new example specifically showcases the use of ogr.ForgejoService to interact with Forgejo, including initializing the service, retrieving pull request commit hashes, and applying custom commit statuses (e.g., success, failure).
• Documentation Update: The examples/README.md file has been updated to include a link to the newly added Forgejo commit status example, making it discoverable for users.

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

Changelog

• examples/README.md
  • Added a new entry linking to the set_commit_status.ipynb example.
• examples/set_commit_status.ipynb
  • New file added, containing a Jupyter Notebook that demonstrates how to use ogr.ForgejoService to set commit statuses.
  • Includes steps for service initialization with a token and instance details.
  • Shows how to retrieve the head commit hash of a specific pull request.
  • Illustrates setting a commit status with CommitStatus.success, a target URL, description, and context.

Activity

• No human activity (comments, reviews) has been recorded on this pull request yet.

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 adds a new example notebook for setting commit statuses on Forgejo. The example is clear and helpful. I've added a couple of suggestions to improve the code style and promote better security practices in the example.

[gemini-code-assist]

For better security practice, it's recommended to load tokens from environment variables rather than hardcoding them, even in examples. This helps prevent accidentally committing sensitive credentials. You can use os.environ.get() for this.

import os
from ogr import ForgejoService
TOKEN = os.environ.get("FORGEJO_TOKEN") or "<paste-your-token-here>"

[centosinfra-prod-github-app]

Build succeeded.
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/packit-service/buildset/da79ace204d943d0925048cc549d0cfa

✔️ pre-commit SUCCESS in 3m 22s
✔️ ogr-tests-pip-deps SUCCESS in 11m 22s

[majamassarini]

🙏🏻

[centosinfra-prod-github-app]

Build succeeded.
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/packit-service/buildset/7619b9736fb0476db35b7744fbfdd916

✔️ pre-commit SUCCESS in 3m 19s
✔️ ogr-tests-pip-deps SUCCESS in 11m 24s

[centosinfra-prod-github-app]

Build succeeded (gate pipeline).
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/packit-service/buildset/a318c1ccd86e452eabbeb9ef4ef71fd0

✔️ pre-commit SUCCESS in 3m 15s