vuejs-jp / che-tsumi Goto Github PK

che-tsumi runs to retry cherry-picking when the default branch is updated.
So deleting the branch that was created when first cherry-picking is needed before doing that.

Hi! We'd like to use che-tsumi to maintain the various translations of the React documentation. I've tested out the bot and the main issue seems to be that some strings are hard-coded:

• the assignReviewers are assigned to vue-jp group (https://github.com/vuejs-jp/che-tsumi/blob/master/index.js#L140)
• the body of the issue created is in Japanese (https://github.com/vuejs-jp/che-tsumi/blob/master/index.js#L76)

It would be great if these can be assigned in an .env file (e.g. ASSIGNED_REVIEWERS).

This bot is great and we hope it gets more use in the React and Vue communities!

We need to upgrade node 10.x or later.

About

Bot 自身が Pull Request を submit した場合、対象となる Issue に "assinged" ラベルを付与し、 Bot 自身を担当者としてアサインしておきたい。

モチベーションとしては、貢献者が行うべき Issue がすぐにわかるようにするため。また、管理者が(Bot が出せる範囲である、コードの微修正やスポンサー追加などの)すぐに捌ける程度の Pull Request を把握しやすくするため。

The package.json says the license is MIT but there isn't a corresponding LICENSE file. The steps to add one are here: https://help.github.com/articles/adding-a-license-to-a-repository/

Currently, chetsumi creates an issue for every item in the RSS feed, even those that are already merged in. For example: https://github.com/reactjs/ja.reactjs.org/issues?q=is%3Aissue+is%3Aclosed

All the [Doc] issues generated by che-tsumi are for commits that already existed when the repo was branched.

You can check that a commit already exists like I did here in my fork: https://github.com/tesseralis/che-tsumi/blob/master/lib/repository.js#L80

che-tsumi-coreみたいなものを作ってche-tsumiはそれに依存する形式に変えたい

背景：
che-tsumiの価値は、ある特定のリポジトリを監視して、違うリポジトリにその変更を追従できること。
それに伴うcoreの機能(lib)はche-tsumi-coreで提供する
プロジェクトごとにやりたいことは違うと思うので、che-tsumiのindex.jsを変更してそれを実現する
che-tsumiのindex.jsはあくまで雛形を提供するもの

@potato4d どう思います？

It's so cool to be able to set up multiple feeds.
(e.g. upstream commit feed)

When upstream commit feed updates, cherry-picking from head commits again, because conflicts may be resolved.

This feature would be cool because it is not good to add "Evan You" or "Chris Fritz" to reviewers😆

Looks like the github library on npm is deprecated: https://www.npmjs.com/package/github

We should update to octokit/rest.js: https://github.com/octokit/rest.js

it's no use to do that.
when cherry-picking, it's better to create branch from upstream's defaut branch directly.