alphagov / alphagov/tech-docs-gem
Proposal: use latest middleman from Github instead of gem release
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 16
- Forks
- 47
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 14
Description
The middleman gem hasn't be released since Oct 2023 (see https://github.com/middleman/middleman/commits/main/CHANGELOG.md).
The community forums have also been pretty quiet for about the same time: https://forum.middlemanapp.com/.
But their dependabot has been happily updating dependencies on their main branch and there are still maintainers merging pull requests with fixes in and tidying up dead code: https://github.com/middleman/middleman/commits/main/.
Seeing as main is actually more of a representation of the middleman code working with the current state of the ruby ecosystem as it is at any given point, it seems like we should move to that instead of the gem.
Contributor guide
No contributing guide indexed for this repository
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 locating the project’s current Middleman dependency declaration, then compare the released gem with the linked GitHub main branch and its recent changes. Verify that using main resolves successfully and that the project’s existing checks still pass; done means the dependency uses the intended source without breaking the gem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, ruby
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100