npm uninstall -g react-native
npm install -g react-native-cli
命令之后，执行react-native run-android/ios仍然会出现
Looks like you installed react-native globally, maybe you meant react-native-cli?
To fix the issue, run:
npm uninstall -g react-native
npm install -g react-native-cli

When looking at rst files, the menu item to display the unrendered source in upper right corner mentions markdown instead of rst.

This method doesn't seem like it's in use, so we should probably remove it?

https://github.com/integrations/slack/blob/0cfaabaa04fe5db6a4d8c33d5d71ad1760a2f32a/lib/messages/issue.js#L24-L26

add java maven extension to gitpod workspace

Exposing category name as a "Change Template" variable would be useful for generating change logs in this format:

- ADDED: X (#100)
- ADDED: Y (#101)
- FIXED: Z (#99)

Relevant documentation:

Variable	Description
$CATEGORY	The category title of the pull request, e.g. Features.

As far as I know you can't do that with Replacers, as you only have one cat

PRs marked as draft (https://github.blog/2019-02-14-introducing-draft-pull-requests/) should be ignored by the stale bot by default, or a settings should allow the bot to ignore them.

Hi,
It will be great if it's allowed to customize the commit message of imgbot, so that we can use conventional commit format without failing commitlint check.

Landscape currently detects 43 code smells here
https://landscape.io/github/OrkoHunter/pep8speaks/17/messages/smell

Not all, but most of them should be easy to fix.

Instead of appearing over/directly under the graph, the scrollbar appears on the bottom of the view as seen in the screenshot. Not sure if this also happens on Android.

We should probably deprecate the workaround token feature as well and then eventually remove it. Should simplify the code a decent amount, since there's logic to specifically detect if push restrictions are enabled.

Originally posted by @bluekeyes in palantir/bulldozer#171 (comment)

Now, typot checks doc file only (.md, .rst). So it will be good to check the comment in source file.

E.g. if you use the GitHub issue templates and automatically apply "bug" or "enhancement", then the bot should not (try to) relabel it.

Humans come before bots!

If the human says this is a bug, the bot should obey. (second robot law) 😆

On the project-bot github repository home page, the example animation at the bottom of the page does not follow the syntax rules for formatting a card. new.issue should be new_issue and arguments should be surrounded by '**'.

This is confusing, and wastes time trying to debug cards that aren't working.

What happened

A common workflow:

1. I make a PR, all the CI goes green, but the overall light is still stuck at yellow
2. I click through to the policy bot UI to see what I need to do to get my thing merged
   
   Unfortun

I believe I've found a case where the DCO enforcement, when there is one unsigned commit, but it is not the last one.

To reproduce, I branch my repo, add a file and commit it unsigned:

git checkout -b dco-test
<Create bugdemo.txt>
git add bugdemo.txt
git commit -a -m "Unsigned commit"
git push --set-upstream origin dco-test

Then I made a change to the bugdemo.txt file and ran:

Ref: https://developer.github.com/v3/activity/events/types/