API development workflow #168
Closed
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
Update unzipper import to ES6
Add swaggerdocs in API and geoprocessing
Fix Shapefile DTO
hotzevzl
force-pushed
the
documentation/api/development-workflow
branch
from
73ac617
to
a3b5e36
Compare
kgajowy
approved these changes
May 12, 2021
aagm
approved these changes
May 12, 2021
|
Thank you so much @hotzevzl for taking time to pull this out. I missed some more defined workflow for us (or at least for me 😅) to follow. Appreciate this |
alexeh
approved these changes
May 12, 2021
|
Replaced by #180 as we needed to rewrite some history of the base branch. |
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.
Some suggestions for meaningful/effective collaboration on tasks: what should be established first, breaking things down, linking to Jira source-of-truth, etc.
Open for discussion (with reason, please 😅)