Conversation
|
Great idea @sempostma. Please also add this to the schemas, as it is a new config field. These files all generate a schema (don't ask me why there's 3):
We will also need a PR on the docs site that documents the new option. I think we should put it above Collections on https://decapcms.org/docs/configuration-options/ |
|
I've updated the schema and added a PR for the docs: decaporg/decap-website#152 |
Head branch was pushed to by a user without write access
213a913 to
e497548
Compare
|
@martinjagodic Rebased on the main branch to fix the minimatch error. |
yanthomasdev
left a comment
There was a problem hiding this comment.
Code LGTM, I'll review the docs next, appreciate the contribution 🙌
|
@sempostma, please run |
54cba3b
martinjagodic
left a comment
There was a problem hiding this comment.
Thanks. I am fixing tests in another PR. When it's merged, this one follows soon after
Summary
A small change that makes the issue url configurable.
In my case, I need this since my client is non-technical. Redirecting them to a Github issue page will just confuse them. A custom url will allow for creating a custom endpoint for automatic reporting of issues.