e49b636497
API: Implement edit via API for projects I've picked up https://github.com/gitlabhq/gitlabhq/pull/8055 fixed the few hound warnings and replaced all double quotes in the spec file where possible. # From the original PR: Implements edit via API for projects. Edit was part of missing features in feature request Full CRUD operations via API for projects. http://feedback.gitlab.com/forums/176466-general/suggestions/3904506-full-crud-operations-via-api-for-projects Feature is implemented using existing UpdateService for projects. Permission to change visibility level and name are checked in addition to check for permission to administer project. Doesn't allow updating project namespace id, because there was existing API-method for transferring project to a group. Documentation added to doc/api/projects.md. Uses API request PUT /projects/:id . Tests included for: 1. Success for changing path 2. Success for changing name 3. Success for changing visibility level 4. Success for changing all other attributes 5. Success for changing name & path to existing name & path but in different namespace 6. Failure if not authenticated 7. Failure if path exists in project's namespace 8. Failure if name exists in project's namespace 9. Failure if not sufficient permission to change name 10. Failure if not sufficient permission to change visibility level 11. Failure if not sufficient permission to change other attributes Allows updating following parameters: * name * path * visibility_level * public * default_branch * issues_enabled * wiki_enabled * snippets_enabled * merge_requests_enabled * description See merge request !310 |
||
|---|---|---|
| .. | ||
| api | ||
| customization | ||
| development | ||
| hooks | ||
| install | ||
| integration | ||
| legal | ||
| markdown | ||
| operations | ||
| permissions | ||
| project_services | ||
| public_access | ||
| raketasks | ||
| release | ||
| security | ||
| ssh | ||
| system_hooks | ||
| update | ||
| web_hooks | ||
| workflow | ||
| README.md | ||
Documentation
User documentation
- API Automate GitLab via a simple and powerful API.
- Markdown GitLab's advanced formatting system.
- Permissions Learn what each role in a project (guest/reporter/developer/master/owner) can do.
- Project Services Integrate a project with external services, such as CI and chat.
- Public access Learn how you can allow public and internal access to projects.
- SSH Setup your ssh keys and deploy keys for secure access to your projects.
- Web hooks Let GitLab notify you when new code has been pushed to your project.
- Workflow Learn how to get the maximum out of GitLab.
Administrator documentation
- Install Requirements, directory structures and manual installation.
- Integration How to integrate with systems such as JIRA, Redmine, LDAP and Twitter.
- Raketasks Backups, maintenance, automatic web hook setup and the importing of projects.
- Custom git hooks Custom git hooks (on the filesystem) for when web hooks aren't enough.
- System hooks Notifications when users, projects and keys are changed.
- Security Learn what you can do to further secure your GitLab instance.
- Update Update guides to upgrade your installation.
- Welcome message Add a custom welcome message to the sign-in page.
- Issue closing Customize how to close an issue from commit messages.
- Libravatar Use Libravatar for user avatars.
- Operations Keeping GitLab up and running
Contributor documentation
- Development Explains the architecture and the guidelines for shell commands.
- Legal Contributor license agreements.
- Release How to make the monthly and security releases.