danger / danger/danger-gitlab-gem

v9.0.0 tag?

Open
#12 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
10
Forks
8
PR merge metrics
No merged PRs in 30d

Description

Since #11 was completed, is it a reasonable time to release a new major version of `danger-gitlab`?

It looks like `danger` itself just had an updated release, so maybe it would be good to tag this around the same time?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the completed work in issue #11 and the referenced updated release of danger. Confirm the intended major-version timing and any repository release conventions. Done means the release decision is settled and the agreed v9.0.0 tag is published.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.