Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Wiki Replica
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Cecylia Bocovich
Wiki Replica
Repository graph
Repository graph
You can move around the graph by using the arrow keys.
3b1c3b570eabfbe994e63be238c611b2a3ee58c1
Select Git revision
Branches
2
master
default
protected
mtg-notes
2 results
Begin with the selected commit
Created with Raphaël 2.2.0
9
Feb
8
5
4
3
2
1
30
Jan
28
27
26
25
21
20
19
18
14
13
12
11
7
6
5
29
Dec
28
27
20
17
11
10
9
8
7
5
3
2
1
24
Nov
23
19
18
17
16
13
10
9
8
4
2
30
Oct
29
28
27
26
21
20
19
14
13
8
7
6
30
Sep
28
23
22
17
16
15
14
10
7
4
Aug
17
Jul
14
13
8
7
6
2
1
30
Jun
27
26
25
24
23
22
18
17
16
mention on-disk files
follow migration docs move
document gitlab pages
small edits to the LVM-less procedure, clarify the distinction
typo
spellcheck puppet howto
move gitlab project wiki here
update puppet-related gitlab CI docs to follow puppet code
mention possible improvements to trocla and hiera
non-normative: two more naming policies
another docs idea
move template issue to the known issues
add more documentation references
notice lack of ENTRYPOINT
add known issues section
braindump docs about CRM mailings
Update ganeti
add another idea for jenkins
publish minutes
fix reference
explicitly mention the pre-req checklist, it seems we forget it often
add explicit hetzner example
expand the reverse DNS documentation
teach users about archetypes
ticket creation failed warning in rt
document tpo/tpa/gitlab#93
template maintenance
explicitely import the audit questions in the template
start documenting jenkins
document irc groups
jenkins is authenticated through LDAP
some weird situation i ended up with last week
you can now comment on any issue by email easily
here's an idea: why don't we skip 3 more steps
document how to post issues.
add budget notes, crossref roadmaps
tolo
crossref pages to static
some todos in the migration remain
fix headings
Loading