This repository was archived by the owner on Jun 15, 2024. It is now read-only.
added GitHub discussions link within FAQ for users to submit questions#116
Open
added GitHub discussions link within FAQ for users to submit questions#116
Conversation
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Description
I think having users post their questions on the CRIPT Excel Uploader repo discussions can be beneficial so users can browse through previous questions and the community can learn from each other.
Unfortunately, this would require a GitHub account and non-technical users would have to be on a technical platform, but I think it shouldn't be too bad and we can try it and see how it goes. The other choice is for us to allow comments on our documentation I think we might need to setup a way for us to get pinged once a question is posted by a user so we can respond to it.
However, GitHub has already built out all of this and is easy to manage, so we can easily use it for now.