feat: add fork workflow pattern and archived actions docs

[CybotTM]

Summary

• Add fork workflow pattern (remote naming, upstream vs intra-fork PRs)
• Document archived TYPO3-CI GitHub Actions with detection method

Context

Learnings from contributing to TYPO3-Documentation/codesnippet via the netresearch/codesnippet fork.

Test plan

• Verify markdown renders correctly

[gemini-code-assist]

Summary of Changes

Hello, 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 enhances the project's documentation by providing essential guidelines for contributing to upstream projects via a fork. It clarifies best practices for managing remotes and crafting pull requests, and introduces a crucial section on identifying and handling archived GitHub Actions to prevent reliance on unmaintained CI workflows. The additions aim to streamline the contribution process and improve the robustness of CI setups.

Highlights

• Fork Workflow Pattern: Added comprehensive documentation on the fork workflow pattern, including remote naming conventions and PR strategies for both upstream and intra-fork contributions.
• Archived GitHub Actions Documentation: Included guidance on how to verify if upstream GitHub Actions are archived, specifically highlighting common archived TYPO3 CI actions and a method to check their status.

Changelog

• skills/github-project/references/repository-structure.md
  • Added a new section 'Fork Workflow Pattern' detailing remote naming conventions and PR strategies.
  • Included a new section 'Archived Upstream Actions' with instructions on how to check for archived GitHub Actions and specific examples related to TYPO3 CI.

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 valuable documentation on fork-based contribution workflows and checking for archived GitHub Actions. The information is clear and useful. I've suggested one improvement to align the remote naming convention with the widely-accepted standard (origin for the fork, upstream for the original repo) to enhance clarity and prevent confusion for contributors.

_{Note: Security Review has been skipped due to the limited scope of the PR.}