| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Also fixes instances in Markdown that broke the rule.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, we used brackets to denote the tier badges,
but this made Kramdown, the docs site Markdown renderer,
show many warnings when building the site. This is now
fixed by using parentheses instead of square brackets.
This was caused by [PREMIUM] looking like a link to
Kramdown, which couldn't find a URL there.
See:
- https://gitlab.com/gitlab-com/gitlab-docs/merge_requests/484
- https://gitlab.com/gitlab-org/gitlab-ce/issues/63800
|
|
|
|
|
| |
First MR in a series updating all redirected links
in CE documentation to the destination URLs
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixing square brackets, links, etc in:
merge_requests.md
vulnerabilities.md
issues.md
issues_statistics.md
pipelines.md
services.md
group_milestones.md
milestones.md
runners.md
changelog.md
issue_workflow.md
elasticsearch.md
api_graphql_styleguide.md
automatic_ce_ee_merge.md
file_storage.md
architecture.md
database_debugging.md
index.md
index.md
frontend_testing.md
pry_debugging.md
vue.md
development_process.md
|
|\
| |
| |
| |
| |
| |
| | |
Allow asynchronous rebase operations to be monitored
Closes #54117
See merge request gitlab-org/gitlab-ce!29940
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This MR introduces tracking of the `rebase_jid` for merge requests. As
with `merge_ongoing?`, `rebase_in_progress?` will now return true if a
rebase is proceeding in sidekiq.
After one release, we should remove the Gitaly-based lookup of rebases.
It is much better to track this kind of thing via the database.
|
|/
|
|
|
|
| |
Many small fixes to api docs which were merged from EE to CE,
and tables cleaned up, as noted in issue
https://gitlab.com/gitlab-org/gitlab-ce/issues/64072
|
| |
|
|\
| |
| |
| |
| | |
Update Project Aliases API documentation
See merge request gitlab-org/gitlab-ce!30288
|
| |
| |
| |
| |
| | |
Fix the example for POST /project_aliases since it doesn't need
the project_id to be URL encoded.
|
|/
|
|
|
|
| |
Squashing a few commits and continuing work
on merging the 12 api docs that have not
been ported to CE yet.
|
| |
|
|\
| |
| |
| |
| | |
Add `--globoff` flag to the curl command for Jobs API.
See merge request gitlab-org/gitlab-ce!30118
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The existing command fail in some cases with the following error `curl: (3) [globbing] bad range specification in column 56`.
This was found when running cURL from a `python:3.7` container that comes with curl version `7.52.1`.
```
root@91963a56cd8f:/# curl --version
curl 7.52.1 (x86_64-pc-linux-gnu) libcurl/7.52.1 OpenSSL/1.0.2r zlib/1.2.8 libidn2/0.16 libpsl/0.17.0 (+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL
```
This doesn't seem to be an issue with `curl 7.58.0` but it doesn't hurt to have that flag enabled.
|
| |
| |
| |
| |
| |
| | |
Linting rule not enabled for now
because tooling produces false
positives.
|
| |
| |
| |
| |
| |
| | |
https://community.atlassian.com/t5/Jira-questions/Is-it-quot-JIRA-quot-or-quot-Jira-quot/qaq-p/681163
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
|
|\ \
| | |
| | |
| | |
| | | |
CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14108
See merge request gitlab-org/gitlab-ce!29604
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Update the newly added documentation to be more precise and
fix the typos.
Add information about Project aliases into permissions doc.
|
| | | |
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
To avoid having to specify an actual password to create users, admins
can now use the `force_random_password` parameter to let Devise generate
a password.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63826
|
|\ \
| | |
| | |
| | |
| | | |
Remove deprecated user routes
See merge request gitlab-org/gitlab-ce!30044
|
| | |
| | |
| | |
| | |
| | |
| | | |
Also release `u` from TOP_LEVEL_ROUTES
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |/
|/| |
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Limit time tracking units to hours
Closes #30355
See merge request gitlab-org/gitlab-ce!29469
|
| |
| |
| |
| | |
Changes migration and all other places the attribute is used
|
| |
| |
| |
| |
| | |
Adds an instance setting to limit display of time tracking
values to hours only
|
|/
|
|
|
| |
Also adds and one linting rule
and makes project conform to it.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This couples the code that transitions the `MergeRequest#merge_status`
and refs/merge-requests/:iid/merge ref update.
In general, instead of directly telling `MergeToRefService` to update
the merge ref, we should rely on `MergeabilityCheckService` to keep
both the merge status and merge ref synced. Now, if the merge_status is
`can_be_merged` it means the merge-ref is also updated to the latest.
We've also updated the logic to be more systematic and less user-based.
|
|\
| |
| |
| |
| | |
Docs: Link issue statistics api endpoint in the docs
See merge request gitlab-org/gitlab-ce!29855
|
| |
| |
| |
| | |
Adds the missing link to issues_statistics api endpoint
|
| | |
|
|/
|
|
|
| |
Updated users API documentation
Moved API level changes to the service level
|
| |
|
|\
| |
| |
| |
| | |
Update GraphQL document to mention that epics are supported
See merge request gitlab-org/gitlab-ce!29777
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
Expose default_git_depth via project API
Closes #62908
See merge request gitlab-org/gitlab-ce!29353
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Enable Get and Update of ci_default_git_depth for
Project API.
Renaming Project#default_git_depth to :ci_default_git_depth
to give more context through the API usage.
Add API documentation
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add spec for task_completion_status
Add test cases for task_completion_status result
Extracted shared samples
Add new spec file for task completion status response
Fix style errors
Add changelog entry
Changed samples to Hashes
Remove test for successful request
Remove not nil expectation
Add task_completion_status to api documentation for issues
Add task_completion_status to api documentation for merge_requests
Refactor spec so it just requests one specific item
Add task_completion_status to Taskable
Simplified task completion status in entities
Refactor spec so it separates status code check and content check
Fix spec description text and field name
|
| |
|
|
|
|
|
| |
Currently, the field used to fill the contents is called "code".
Also "visibility" is now required.
|
|\
| |
| |
| |
| |
| |
| | |
Automatically update MR merge-ref along merge status
Closes #58495
See merge request gitlab-org/gitlab-ce!28513
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This couples the code that transitions the `MergeRequest#merge_status`
and refs/merge-requests/:iid/merge ref update.
In general, instead of directly telling `MergeToRefService` to update
the merge ref, we should rely on `MergeabilityCheckService` to keep
both the merge status and merge ref synced. Now, if the merge_status is
`can_be_merged` it means the merge-ref is also updated to the latest.
We've also updated the logic to be more systematic and less user-based.
|
|/
|
|
|
|
| |
We can query namespaces, and nested projects.
Projects now exposes statistics
|