kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/doc
History
Douwe Maan c9a7cc4b37 Merge branch '2364-fallback-to-in-reply-to-header' into 'master' 
Fall back to In-Reply-To and References headers when sub-addressing is not available

_Originally opened at !3024 by @dabit._

- - -

Fixes #2364 

Summary of the changes:
- No more need to have the `%{key}` placeholder in the `incoming_email.address`
- The fallback message id format is `reply-[key]@[gitlab_host]` (reminder: it doesn't have to be a real email address)
- The fallback message id that includes the reply key is added to both `References` header
- Documentation for the "Reply by email" feature updated

See merge request !3305
2016-03-30 16:16:37 +00:00
..
administration Update LDAP docs [ci skip] 2016-03-22 15:35:27 -05:00
api Merge branch 'mariusz_jachimowicz/gitlab-ce-i_14415_expose_label_description' into 'master' 2016-03-29 16:21:16 -04:00
ci Merge branch 'feature-ci-only-except-trigger' into 'master' 2016-03-22 09:42:40 +00:00
customization Branded login page also in CE 2016-02-26 15:50:51 +01:00
development SCSS Style Guide fixes. 2016-03-23 14:39:12 -06:00
gitlab-basics Remove redundant word 2016-03-22 13:11:18 +02:00
hooks Use relative links in doc, fix broken generated HTML links 2016-03-17 00:35:53 +01:00
incoming_email Improve and finish the fallback to the In-Reply-To and References header for the reply-by-email feature 2016-03-25 13:05:15 +01:00
install Gitlab-workhorse tags have "v" now 2016-03-21 13:13:34 +01:00
integration Merge branch 'master' of gitlab.com:gitlab-org/gitlab-ce 2016-03-28 23:22:15 +02:00
intro Fix grammar in intro guide 2016-03-22 12:56:52 +02:00
legal Reformats confusing '[named here]' section for 3rd party code attribution 2016-02-17 17:13:06 +00:00
logs
markdown Capitalize Rouge mentions 2016-03-10 16:12:50 -03:00
migrate_ci_to_ce Update ci to ce doc to make it clearer when you are done if you don't want to keep your data. 2015-10-05 16:39:58 +02:00
monitoring/performance Grafana installation and configuration documentation. [ci skip] 2016-03-22 13:34:05 -05:00
operations
permissions Refactor external users docs 2016-03-17 09:24:06 +02:00
profile Add references to the rouge gem library 2016-01-25 22:36:44 +01:00
project_services Fixed headers for anchors 2016-03-07 16:29:22 -05:00
public_access Add docs on group visibility 2016-03-22 12:36:43 +02:00
raketasks Reload the schema before restoring a database backup 2016-03-21 21:16:34 -05:00
security Use relative links in doc, fix broken generated HTML links 2016-03-17 00:35:53 +01:00
ssh Fixed Window's commands for SSH Help. 2016-02-06 12:17:12 +00:00
system_hooks Include user_username in user_(add_to/remove_from)_(project/group) system hooks. 2016-01-07 12:54:54 -05:00
update Fix order of steps to prevent PostgreSQL errors when running migration [ci skip] 2016-03-22 20:55:19 -03:00
web_hooks Fix typos in webhooks docs. 2016-03-27 18:10:10 +00:00
workflow Clarify LFS configuration 2016-03-24 10:00:27 -05:00
README.md Merge branch 'update_ldap_docs' into 'master' 2016-03-28 16:36:42 +00:00

README.md

Documentation

User documentation

  • API Automate GitLab via a simple and powerful API.
  • CI GitLab Continuous Integration (CI) getting started, .gitlab-ci.yml options, and examples.
  • GitLab as OAuth2 authentication service provider. It allows you to login to other applications from GitLab.
  • GitLab Basics Find step by step how to start working on your commandline and on GitLab.
  • Importing to GitLab.
  • Markdown GitLab's advanced formatting system.
  • Migrating from SVN Convert a SVN repository to Git and GitLab
  • Permissions Learn what each role in a project (external/guest/reporter/developer/master/owner) can do.
  • Profile Settings
  • 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.
  • Webhooks Let GitLab notify you when new code has been pushed to your project.
  • Workflow Using GitLab functionality and importing projects from GitHub and SVN.

Administrator documentation

Contributor documentation

  • Documentation styleguide Use this styleguide if you are contributing to documentation.
  • Development Explains the architecture and the guidelines for shell commands.
  • Legal Contributor license agreements.