imagej / imagej/imagej.github.io
Build with GitHub actions
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 203
- Avg merge
- 1h 50m
- Merged PRs (30d)
- 1
Description
By default, GitHub pages are built with the gh-pages gem which locks in Jekyll to 3.9 - which can be very slow.
We can change the gemfile to use a newer, faster jekyll and experiment with other plugin versions, but the page will still eventually be built on the GH-side with 3.9. So eventually it would be reasonable to migrate to GitHub actions
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
Review the Gemfile and the linked Jekyll GitHub Actions guidance first; the issue does not name a more specific configuration file or test. Done means the site builds through GitHub Actions instead of the GitHub Pages default Jekyll 3.9 path, with the relevant plugin versions working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, jekyll
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100