# Renovate Config Repository Example

This directory contains example files for creating a separate `renovate-config` repository that will run Renovate Bot centrally for all your repositories.

## Quick Start

1. Create a new repository called `renovate-config` on your Gitea instance
2. Copy these files to that repository:
   ```
   renovate-config/
   ├── config.js
   ├── .gitea/
   │   └── workflows/
   │       └── renovate.yml
   ├── README.md
   └── .gitignore
   ```

3. Follow the setup instructions in [`../RENOVATE.md`](../RENOVATE.md)

## Files Included

### config.js
Main Renovate configuration file that defines:
- Platform (gitea)
- API endpoint
- Repository discovery (autodiscover B4L/*)
- Rate limiting
- Caching

### .gitea/workflows/renovate.yml
Gitea Actions workflow that:
- Runs daily at 2 AM UTC
- Uses official Renovate container
- Can be triggered manually
- Reads config.js for settings

### README.md
Documentation for the renovate-config repository explaining setup and usage.

## Important Notes

- This is a **template** - copy to a new repository, don't use in place
- Edit `config.js` to match your Gitea endpoint
- Edit `autodiscoverFilter` to match your organization/user
- Add `RENOVATE_TOKEN` as repository secret
- Optionally add `GH_TOKEN` for GitHub releases (not `GITHUB_TOKEN` - see Gitea naming rules below)

### Gitea Secret Naming Rules

Gitea has specific rules for secret names:
- Must contain only alphanumeric characters ([a-z], [A-Z], [0-9]) or underscores (_)
- Cannot start with `GITHUB_` or `GITEA_` prefix
- Cannot start with a number
- Not case-sensitive
- Must be unique at the repository level

**Therefore**: Use `GH_TOKEN` instead of `GITHUB_TOKEN` for the GitHub access token.

## See Full Documentation

For complete setup instructions, see:
- [RENOVATE.md](../RENOVATE.md) - Full Renovate documentation
- [Official Gitea Tutorial](https://about.gitea.com/resources/tutorials/use-gitea-and-renovate-bot-to-automatically-monitor-software-packages)