ldtteam / ldtteam/OperaPublicaCreator
List of wanted features
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Just my ideas so we have some pinned list, feel free to modify the list as you want
- generate proper ranges for deps in mods.toml, so we can finally do binary-breaks in middle of version
- fix setup-gradle cache in actions, so we dont have to do recomp cycle every build (at least for our branches, idc about forks rn)
- jcc binary checking for PRs, bind that to automatical version bump
- file check for AT #6
- AT cleanup task, requires support in neo?
- local builds have correct version, ie. if gradle.props modVersion == "fromTag" then act like normal publish
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
This issue combines several independent tasks involving mods.toml, gradle.props, GitHub Actions setup-gradle caching, jcc checks, and AT cleanup. First split the checklist into focused issues, then inspect the relevant Gradle and workflow configuration for each one; each task is done only when it has separate scope and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100