Masato Ohba

Add support for Ruby 3.0

1

What do you think about Ruby 3.0 support? I'm not sure about this repository's policy, but thought it's a good start point to run tests with Ruby 3.0 on CI.

@onk @motemen ## Issue Closes #54 ## Changes As described in https://github.com/x-motemen/git-pr-release/issues/54, I added `aggregate_labels` feature. - Add `pr-release.aggregate_labels` config (or `GIT_RELEASE_PR_AGGREGATE_LABELS`). - It accepts boolean-ish value: `"true"` or anything...

[Proposal] Aggregate labels from pull requests

1

Hello maintainers. @motemen @onk If possible, I hope this gem would have a feature that determines labels to be added to a created pull request by aggregating labels on merged...

The current tech stacks are a bit behind the cutting edge. I'm planning to update and migrate some. - Bump Ruby 3.1 - Bump Rails 7.0 - Bump TypeScript 4.6...

Enable to select all languages that GitHub recognize

2

Seemingly, there are so many other languages in this world. 

ref https://github.blog/2019-02-14-introducing-draft-pull-requests/ I'm thinking whether the bot should omit draft pull requests or not.

Ruby 3.1: Add specs for `Time#new` `in` keyword

2

## Issue * [Write specs for new Ruby 3.1 features and changes #923](https://github.com/ruby/spec/issues/923) ## Change This pull request covers the spec below. > * [ ] Time.new now accepts optional...

## Problem When I run `reviewdog/action-rubocop`with `rubocop_flags: --server` option, `reviewdog` command fails to parse its result. ``` Running rubocop with reviewdog 🐶 ... reviewdog: parse error: failed to unmarshal rdjson...