or

1. Click your "user dropdown" (top-right corner of every page)
2. Click "Your repositories"

The URL should be

https://github.com/fregante?tab=projects&type=source

But is

https://github.com/fregante?tab=projects

We have a bunch of features we can move from the Beta section to the permanent docs.

I think everything under https://www.netlifycms.org/docs/beta-features/ except i18n and Nested collections can be moved

It would make sense to move each feature at a time to make sure we're not cluttering the docs

📋 Description

The OpenBuildService is the free Linux packaging platform from openSUSE.
For my usecase, I'd only need the build status from one package in one repository, but it has a lot more api endpoints than that.

Example badge: https://img.shields.io/badge/openSUSE%20Tumbleweed-Succeeded-success

🔗 Data

• API Doc: https://build.opensuse.org/apidocs/index

问题类型

Feature Request

PicGo的相关信息

Windows 10 1909 18363.535
picgo 2.2.0

问题重现

功能请求

能否在上传区各个图床标题上以及图床设置中各个图床标题上，添加上图床管理页面的链接，单击后可直接打开浏览器跳转到图床管理页面？
如下图所示

Describe the feature or problem you’d like to solve

Microsoft released Windows Terminal Preview yesterday. It would be nice if GitHub Desktop was able to detect it.

Proposed solution

Adds an option to the shells available to use.

Additional context

N/A

JS 配置如下：

 var gitalk = new Gitalk({
            clientID: '3654916*****0c0038c28',
            clientSecret: 'd90d031a*****0e0fa4c7fe2fae747b96b',
            repo: 'Strange-AI.github.io',
            owner: 'Strange-AI',
            admin: ['jinfagang', 'Strange-AI'],
            id: vm.codeId,
            distractionFreeMode: false
        });
        gitalk.render('gitalk-conta

Describe the Error

behavior-bot is not working on config.yml file

url.parse is deprecated, and is likely to be removed in a new version of Node.js

Use of the legacy url.parse() method is discouraged. Users should use the WHATWG URL API. Because the url.parse() method uses a lenient, non-standard algorithm for parsing URL strings, security issues can be introduced. Specifically, issues with host name spoofing and incorrect handling of usernames and p