-
Whenever the Wharf API or any provider responds with a problem.Response type then the frontend should show it in a good way.
- Title
- Detail
- Type (suddle)
- Link to documentation (using the t…
-
> Depends on #12 & #15
Projects are currently mapped to their corresponding provider via name. Name can change, such as when a project is moved, but ID does not.
This is such a fundamentally imp…
-
> Depends on #12
Projects are currently mapped to their corresponding provider via name. Name can change, such as when a project is moved, but ID does not.
This is such a fundamentally impactfu…
-
Add documentation for https://github.com/iver-wharf/wharf-provider-github/issues/15
-
Add documentation for https://github.com/iver-wharf/wharf-provider-gitlab/pull/15
-
Add documentation for https://github.com/iver-wharf/wharf-provider-azuredevops/pull/14
-
When importing from either provider, you need an access key.
The access this key needs has to be documented, as it's an obvious question that arises.
Todo:
- Look at the code (https://github.com/…
-
Ex: https://quay.io/repository/iver-wharf/wharf-provider-azuredevops/create-notification, but for all the repos
Suggest sending them to a teams channel
Depends on https://github.com/iver-wharf/wha…
-
> Based on [RFC-0011: quay.io](https://iver-wharf.github.io/rfcs/published/0011-quay.io)
Docker images are currently stored in our internal docker repo. We want these to be publicly available.
W…
-
## 🐛 Bug Report
No `locality` is retrieved from coordinates lat:51.531301199999994, lon: -0.0956268 but `name`, `thoroughfare`, `postalCode` and `country` are.
![Capture d’écran 2020-05-08 à 1…