'namespace' should be exposed via the API #2460

Merged
merged 1 commit into from Jan 16, 2013

Conversation

Projects
None yet
5 participants
Contributor

calmh commented Jan 2, 2013

Since it's now an integral part of the project name, it should be
visible via the API.

@calmh calmh 'namespace' should be exposed via the API
Since it's now an integral part of the project name, it should be
visible via the API.
0f07922
Contributor

m4tthumphrey commented Jan 2, 2013

👍

Contributor

riyad commented Jan 2, 2013

This should be solved together with #2445

@randx randx added a commit that referenced this pull request Jan 16, 2013

@randx randx Merge pull request #2460 from calmh/expose-namespace
'namespace' should be exposed via the API
4c93d77

@randx randx merged commit 4c93d77 into gitlabhq:master Jan 16, 2013

1 check failed

default The Travis build failed
Details
Contributor

Xylakant commented Feb 20, 2013

As far as I can see this is only a partial fix for the issue. The PR referenced as a fix does not allow creating projects with a namespace on the API since namespace or namespace_id are supported here https://github.com/gitlabhq/gitlabhq/blob/master/lib/api/projects.rb#L26

See also #2445 (comment)

@randx randx pushed a commit that referenced this pull request May 10, 2016

@rymai rymai Merge branch '2460-3690-support-multiline-tag-message' into 'master'
Support multi-line tag messages

_Originally opened at !2853 by @clns._

- - -

Tag messages in Git can include a short summary of what changes are included in a release and any other relevant information. So I think GitLab should support multi-line tag messages, both in the "New Tag" interface and when viewing the tag.

Also a non-technical user could use GitLab's interface to create releases, but at the moment this is impossible because he cannot enter a multi-line message. This would've been very handy, otherwise he would need to do it from the command line or other GUI program, which is not something a non-technical user has access to or knows how to do.

This merge request adds support for multi-line tag messages. Below are the impacted screens. Let me know if I should change anything.

This would close #3690 and #2460

![image](/uploads/d33bede1141bfb10c5d9c301ee1cb0ec/image.png)
![image](/uploads/ebfea358c1a5986e7b95ad31748f7a6a/image.png)

See merge request !3833
4453104
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment