You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the current templates and onboarding documentation work. For people unfamiliar with FSC-PS and GitHub, I propose a more simplified template and onboarding.
The template would just be for D365FSC extensions. It would have one build action and just the minimum of .json files to support that. Documentation for the template would explain
how to set it up
how to connect to it from a development environment
how to add a simple extension
how to run the build for that extension
Future work could add similar templates for commerce extensions. It could also add documentation that show how to add the other stuff (CI, CD, repo update, ...).
Aside from a more simplified onboarding, I also think this would remove concerns around allowing a third party access to the repo (the repo update) or having to upload an existing extension to a public url (for the import).
The text was updated successfully, but these errors were encountered:
I think the current templates and onboarding documentation work. For people unfamiliar with FSC-PS and GitHub, I propose a more simplified template and onboarding.
The template would just be for D365FSC extensions. It would have one build action and just the minimum of .json files to support that. Documentation for the template would explain
Future work could add similar templates for commerce extensions. It could also add documentation that show how to add the other stuff (CI, CD, repo update, ...).
Aside from a more simplified onboarding, I also think this would remove concerns around allowing a third party access to the repo (the repo update) or having to upload an existing extension to a public url (for the import).
The text was updated successfully, but these errors were encountered: