go-gitea/gitea#11032 will output unicode emoji from tokens and attempting to save such a emoji into a utf8 table will result in error 500:

CreateIssueComment: Error 1366: Incorrect string value: '\xF0\x9F\x91\x8E' for column 'content' at row 1

I think we should:

1. default new installs to utf8mb4
2. mention in the release notes that MySQL users are e

I'm probably missing something obvious, but neither the website nor this repo has any documentation.

Is this a markdown editor I can embed in my "classic" rendered (html rendered by server) websites?

Do I have to build my own version?
Can I use npm to import it?
Is there any documentation?

Hi Guys,
This is informational, but upgrading to the latest from versions prior to 11.11.0 fail to update the db schema for postgres instances.
e.g.
"Your current database version is too old to be migrated. You should upgrade to GitLab 11.11.0 before moving to this version. Please see https://docs.gitlab.com/ee/policy/maintenance.html#upgrade-recommendations"
Thought it might be worth mention

I cannot figure out how to use properly danger on circleci 2.0 with workflows

Support I have a linear workflow where I bundle my app / install libraries (build job) and then run the tests in parallel. (I'm taking Ruby/Rspec as an example).

How can I execute Danger to report test failures on all containers ?

Currently if a job fails on circleCI, the dependent jobs are not ran (ie if I

What Renovate type are you using?

I am using Renovate in a private project hosted on Gitlab.com

Describe the bug

It's not a bug but a simple typo. If you start using Renovate, it will usually create a "Pin dependencies" pull request. The PR template contains a

New Relic reports the E_WARNING below. I also have the issue in #703, maybe they are related?

Stack trace

E_WARNING: file_get_contents(/opt/wordpress/wp-content/tmp-readme.txt): failed to open stream: No such file or directory
in file_get_contents called at /opt/wordpress/wp-content/plugins/github-updater/vendor/class-parser.php (168) 
in WordPressdotorg\Plugin_Directory\Readme\Parser

If an incorrect URL is opened, please provide the following so we can write a test:

Example clone URL:

https://aur.archlinux.org/git-open-git.git or ssh://[email protected]/git-open-git.git

Example branch name:

master

Expected web URL:

https://aur.archlinux.org/packages/git-open-git

It will be a simple fix. We can add a simple if condition with a regex to check

reviewdog/reviewdog#405 introduced the -tee option, but there is no mention of the feature in the readme. This would be helpful info for us who are trying to implement/debug this tool

Per the tox documentation is mentions that the parallel_show_output setting is a global [tox] setting however this doesn't seem to be the case, i.e., if one's tox.ini file is of the form:

[tox]
parallel_show_output = true

then running tox --parallel auto does not show any output.

According to t

Points to cover:

• playbook for how to get started with testing
• differences between testing locally vs staging vs production
• how to configure tests for different environments

@johngrimsey thank you for the idea! Please feel free to comment if I missed something.

Description of the problem, including code/CLI snippet

Documentation is missing an example how to make use of project import parameters.
The Gitlab-API supports these parameters (name,file,path,overwrite)

Expected Behavior

It would be good to add an example to the documentation (if those parameters are supported)

Actual Behavior

Specifications

• python-gitlab versi

We add gitlab bot in group but all of the message is not necessary for everyone.
so i thinks it's very good feature that give the usernames of users to bot and bot mention the user if that pm related to that user.

Git knows to translate git $var to git-$var if it isn't a built-in command.
Thus all of the examples could use git chglog instead of git-chglog.
This has the advantage of greater familiarity, potential integration with .gitconfig and less explaining to do.

$ git repo --help
No manual entry for git-repo
$ git-repo --help
....

It looks like it was solved in the upstream (spf13/cobra#669) but your version is pinned at v0.0.0-20180412120829-615425954c3b (I'm not a gopher, so i'm not 100% sure that that's the reason)

See scala/scala-xml#359 (comment).

The GitLab API normally limits the list of issues to 100 entries per request, with a default of 20. This means that Issues::all() and Project::issues() by extension only return the first 20 issues of a project by default, which is surprising given their respective names. It'd be nice if the docs stated this fact, and provided a workaround.

I'd be willing to write a PR for this.

Hi,
Now that we have nested group in gitlab since v9 it would be very interesting to implement it in gitlab-mirrors.
Would be super useful, as we could mirror several git repositories of a unique project to a unique sub group in a base "gitlab-mirrors" group (wow!)

Cheers

https://github.com/google/starlark-go/blob/master/doc/spec.md

It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.

Like in #137 we should provide build context information.