-
Notifications
You must be signed in to change notification settings - Fork 1.8k
A reorganization of the platform-samples repo #785
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
ALSO: There are links to this repo in our official docs and those link changes would need to be coordinated before any merge goes through. I opened this as a DRAFT PR. |
Ultimately, looking to make this more intuitive where things should fall into place. And with better organization, people intuitively knowing where to look for solutions as well. I would like to have README's in each folder that also clarify why each folder exists, whether that is for organizing the content, or to describe a solution. The FastTrack team will have a lot of scripts to move in here once we get the organization figured out. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leave a
Leave a comm |
Hey guys, I've made some changes to the platform-samples repository that moves in to a direction of more formal organization.
I've also added an archive folder to move things that are no longer relevant into a bucket that in my mind, would eventually get deleted/removed.
I'm not sure I have everything ironed out, but wanted to get the ball rolling with some feedback.
For reference, here is the issues we are tracking these changes:
Issue-432
Issue-433