Skip to content
#

gitlab

Here are 1,652 public repositories matching this topic...

dalu
dalu commented Mar 21, 2020

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?

LewS
LewS commented Nov 11, 2019

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

Startouf
Startouf commented Jun 21, 2018

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

renovate
tox
krathow
krathow commented Mar 31, 2020

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
CosmicToast
CosmicToast commented Oct 6, 2019

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.

ijks
ijks commented May 1, 2018

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.

agola

Improve this page

Add a description, image, and links to the gitlab topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the gitlab topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.