Tag the core modules nsw-srilanka pins to pseudo-versions

Open
#408 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
release

Research direction

Start by reviewing the module layout and current release or tagging process for the root module, shared, configyaml, htmlgen, and json. Check the core extraction tracked in OpenNSW/nsw-srilanka#1248 to understand which module moves need tags. Done when each listed module's current main is tagged and future move PRs keep affected modules tagged so nsw-srilanka can use tags instead of pseudo-versions.

Written by the indexing model from the issue text.

Description

nsw-sl cleanup Type/Improvement
Current Limitation

OpenNSW/nsw-srilanka pins several core modules to pseudo-versions instead of tags: the root module (github.com/OpenNSW/core), shared, configyaml, htmlgen and json. The core extraction moves code into core in many steps, and the moves themselves use pseudo-versions of core commits.

Suggested Improvement

Tag the current main of each of these modules, and keep tagging each module a move PR changes, so nsw-srilanka never needs a pseudo-version.

Additional Context

After the moves in the core extraction tracked in OpenNSW/nsw-srilanka#1248.

Dominant language
Go
Stars
6
Forks
8
Avg merge
21h 36m
Merged PRs (30d)
42

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenNSW/core

All issues in OpenNSW/core

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.