From e43920bc87853f9353e93846916e5f74289dcd64 Mon Sep 17 00:00:00 2001 From: Michael Muré Date: Sat, 4 Apr 2020 14:09:27 +0200 Subject: readme: fix image links --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 5aaa2e0c..fd47392a 100644 --- a/README.md +++ b/README.md @@ -68,7 +68,7 @@ There is multiple ways to use `git-bug`:
Native workflow

- Native workflow + Native workflow

This is the pure `git-bug` experience. As you would do with code, push and pull your bugs between git remotes. @@ -77,7 +77,7 @@ This is the pure `git-bug` experience. As you would do with code, push and pull
Bridge workflow

- Bridge workflow + Bridge workflow

As `git-bug` has bridges with other bug-trackers, you can use it as your personal local remote interface. Sync with `git bug bridge pull` and `git bug bridge push`, work from your terminal, integrate into your editor, it's up to you. And it works offline ! @@ -86,7 +86,7 @@ As `git-bug` has bridges with other bug-trackers, you can use it as your persona
Web UI workflow (WIP)

- Web UI workflow + Web UI workflow

Often, projects needs to have their bug-tracker public and accept editions from anyone facing a problem. To support this workflow, `git-bug` aims to have the web UI accept external OAuth authentication and act as a public portal. However the web UI is not up to speed for that yet. Contribution are very much welcome! -- cgit