[E] To bypass GitHub's limit of 100 MB you can use Git Large File Storage (Git LFS). It stores references to your file in the repo by creating a pointer file. However, the actual file is going to be stored at a different location.
[C] Configuring the retention period for GitHub Actions artifacts and logs in your organization You can configure the retention period for GitHub Actions artifacts and logs in your organization.
By default, the artifacts and log files generated by workflows are retained for 90 days before they are automatically deleted. You can adjust the retention period, depending on the type of repository:
For public repositories: you can change this retention period to anywhere between 1 day or 90 days.
For private repositories: you can change this retention period to anywhere between 1 day or 400 days.
When you customize the retention period, it only applies to new artifacts and log files, and does not retroactively apply to existing objects. For managed repositories and organizations, the maximum retention period cannot exceed the limit set by the managing organization or enterprise.
Reference:
https://gitprotect.io/blog/github-storage-limits/
https://docs.github.com/en/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization

The best way for an enterprise to control which GitHub Actions run is by creating a list of approved actions as an enterprise policy. This approach restricts workflows to only use the actions that are explicitly allowed, ensuring security and compliance within the organization.
Note: To allow a specific list of actions at the GitHub Enterprise level, an administrator must navigate to Enterprise > Policies > Actions and select "Allow select actions". Then, from the dropdown menus, they choose "Allow selected actions and reusable workflows" and add the desired actions to the allowed list using the format OWNER/REPOSITORY@TAG-OR-SHA.
These actions can also include local actions, actions from specific organizations, or specific tags or commit SHAs.
Reference:
https://docs.github.com/en/enterprise-cloud@latest/admin/enforcing-policies/enforcing-policies- for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise

To trigger a GitHub Actions workflow on both push and pull request events, use the on key with a list of the events:
on:
push:
branches: [ "main" ]
pull_request:
branches: [ "main" ]
Key Details:
Events: You can list multiple events under on. This setup ensures the workflow runs whenever code is pushed to main or when a PR is opened/updated against main.
Activity Types: By default, pull_request triggers on opened, reopened, and synchronize (new commits to the PR).
Filtering: You can further refine these triggers by adding specific paths, tags, or different branches to avoid unnecessary runs Incorrect:
[Not A]
The push event is for the dev branch only.
[Not B]
Has only the push event.
[Not C]
Has only the push event.
Reference:
https://blog.devops.dev/automate-your-workflow-a-guide-to-ci-cd-with-github-actions-3f395d60ba69

To ensure your reusable GitHub Actions workflow template appears in the New workflow interface (also known as the starter workflow picker), it must be stored in a specific directory within a special repository in your organization.
Required Storage Location
Repository Name: .github (This must be a public repository at the root of your organization).
Directory Path: workflow-templates.
Note:
Essential Files to Include
For the template to be correctly indexed and displayed in the interface, you must include two files in the workflow-templates directory:
The Workflow File: A standard YAML file (e.g., ci-template.yml) containing the workflow definition.
The Metadata File: A JSON file that must have the same name as the workflow file but with a .properties.json extension (e.g., ci-template.properties.json).
Reference:
https://docs.github.com/en/[email protected]/actions/using-workflows/creating-starter- workflows-for-your-organization

Setting an output parameter
Sets a step's output parameter. Note that the step will need an id to be defined to later retrieve the output value. You can set multi-line output values with the same technique used in the Multiline strings section to define multi-line environment variables.
echo "{name}={value}" >> "$GITHUB_OUTPUT"
Example of setting an output parameter
This example demonstrates how to set the SELECTED_COLOR output parameter and later retrieve it:
- name: Set color
id: color-selector
run: echo "SELECTED_COLOR=green" >> "$GITHUB_OUTPUT"
- name: Get color
env:
SELECTED_COLOR: ${{ steps.color-selector.outputs.SELECTED_COLOR }}
run: echo "The selected color is $SELECTED_COLOR"
Reference:
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-commands