meilisearch / meilisearch/meilisearch-php
Ensure bug fixes from v1 are consistently brought into v2
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 757
- Forks
- 125
- Avg merge
- 6d 8h
- Merged PRs (30d)
- 2
Description
This might not be required if we have little updates on v1.x in the future, but I'm opening this to keep track.
Description
To ensure bug fixes from v1 are consistently brought into v2, we could create a scheduled GitHub Actions workflow that runs weekly to open a pull request to merge the 1.x branch into main.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's existing GitHub Actions workflows and the relationship between the 1.x and main branches. Implement a weekly scheduled workflow that opens a pull request merging 1.x into main, then verify that the workflow runs with the required permissions and creates the expected pull request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, php
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100