Reuse Directory #30
Open
Reuse Directory #30
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
REP-216 reuse tweaks
…e-directory-frontend Update labels for reuse directory
# Conflicts: # pages/index.vue
…weaks Reuse directory style tweaks
Apply fix from Reuse Directory to Repair Directory, but also fix the fix
REP-227 borough area
# Conflicts: # components/Business.vue # components/BusinessModal.vue
|
Kudos, SonarCloud Quality Gate passed!
|
To try and increase likelihood of tracking being allowed in an embed.
|
Kudos, SonarCloud Quality Gate passed!
|
…directory-nuxt into REP-75_leaflet
REP-75 Switch from Google Maps to Leaflet
Merging develop into develop-reuse
|
Kudos, SonarCloud Quality Gate passed!
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is not intended to merge yet
It's an easy way to see the changes made on the develop-reuse branch for the Reuse Directory.
Once this is stable, we would take a branch off it for production-reuse, and switch the live site to deploy that. Then we'd delete this PR.