Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
R
Reflow Amsterdam
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
code
Reflow Amsterdam
Repository graph
Repository graph
You can move around the graph by using the arrow keys.
c4eb9dc7c62081a7d927760570c5ea1125e8ebb7
Select Git revision
Branches
3
bonfire2
main
default
protected
ping
3 results
Begin with the selected commit
Created with Raphaël 2.2.0
24
Jun
30
May
3
25
Mar
17
15
11
3
1
28
Feb
25
9
1
28
Jan
27
14
13
11
10
7
6
4
3
24
Dec
21
15
10
7
6
3
30
Nov
29
26
19
18
8
5
2
1
8
Oct
7
27
Sep
24
13
10
24
Aug
23
20
19
17
10
6
5
3
2
30
Jul
29
27
26
19
Readme
main
main
Adding version 2 of the isolation gown flow
Adding one more agent and the data from the schema made by Ger
Merge branch 'main' of https://gitlab.waag.org/code/reflow_amsterdam
Name change in resource
liters times 1000
date error handling
updated script content
ping
ping
removed new_extra from script
ping date
vrije ping
or is io rescue
impactg
calculations
phone first layout
multiple quotes
visual timeline
photo layout
Adding Maison et Objet visualisation
Adding transfer to recycler
template bug
items owned
ping and cms overview
sort resources by activity, shore more information
links back to application from bot
chat script updates, welcome text on item page, error handling
Pushing the license
Shorten simulation duration to 15 days
Update Readme
Adding template config file
Wrap call because of Telegram::Bot::Exceptions::ResponseError: Telegram API has returned the error. (ok: "false", error_code: "502", description: "Bad Gateway")
Begin rescue block for retrieving resource (dialog was called with an empty agent.dialog_subject and bot crashed)
Update a couple of comments
Adding possibility to read users from .config.yaml
skip forgery protection
config bot settings
translated narrative page to english
create resource events
update resource from chat including photo
reset state machine correctly on start, create summary
Loading