summaryrefslogtreecommitdiff
path: root/doc/development/fe_guide/index.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/development/fe_guide/index.md')
-rw-r--r--doc/development/fe_guide/index.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/development/fe_guide/index.md b/doc/development/fe_guide/index.md
index b2a6189ff83..c9dd9f45abf 100644
--- a/doc/development/fe_guide/index.md
+++ b/doc/development/fe_guide/index.md
@@ -59,13 +59,15 @@ branch from `new-feature`, let's call it `new-feature-step-2` and repeat the pro
**Tips**
- Make sure `new-feature` branch is always synced with `master`: merge master frequently.
- Do the same for the feature branch you have opened. This can be accomplished by merging `master` into `new-feature` and `new-feature` into `new-feature-step-*`
-- Avoid rewriting history.
+- Avoid rewriting history.
### Share your work early
1. Before writing code guarantee your vision of the architecture is aligned with
GitLab's architecture.
1. Add a diagram to the issue and ask a Frontend Architecture about it.
+
![Diagram of Issue Boards Architecture](img/boards_diagram.png)
+
1. Don't take more than one week between starting work on a feature and
sharing a Merge Request with a reviewer or a maintainer.