-
Notifications
You must be signed in to change notification settings - Fork 9
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
Changing the Repo's v5.1.0 branch to Main #241
Conversation
* Create Crisis Event Entity https://tracker.ed-fi.org/browse/DATASTD-2165 * Update DisplacedStudentStatusDescriptor.xml
* Descriptors https://tracker.ed-fi.org/browse/DATASTD-2182 * Small update to definition language Eligibility due to desegregation
* Change links to new Tech Docs * Add a security file * code owners file * New scorecard action * Explicitly set permissions * Scorecard badge * Codeowners correction
Co-authored-by: Mustafa Yilmaz <[email protected]>
https://tracker.ed-fi.org/browse/DATASTD-2191 Co-authored-by: Mustafa Yilmaz <[email protected]>
* [DATASTD-2190] Update XSD files * [DATASTD-2190] Add StudentHealth Sample data [DATASTD-2190] Add StudentHealth sample data * [DATASTD-2190] Update references to 5.1.0 --------- Co-authored-by: Mustafa Yilmaz <[email protected]>
* [DATASTD-2160] Add StudentHealth Descriptors * [DATASTD-2160] ImmunizationType Descriptor Definition Update * [DATASTD-2160] Add StudentHealth Descriptors * [DATASTD-2160] ImmunizationType Descriptor Definition Update * Namespace updates from 5.0.0 to 5.1.0 While working on the last correction for the Student Health PR, I have implemented Schema Bulk XSD, Sample Data and Descriptor update to 5.1.0 as requested in DATASTD-2196. * Namespace Updates - continued --------- Co-authored-by: Stephen Fuqua <[email protected]>
Co-authored-by: Mustafa Yilmaz <[email protected]>
* [DATASTD-2199] Update for Data Standard 5.1 * [DATASTD-2199] Update UML Diagram --------- Co-authored-by: Mustafa Yilmaz <[email protected]>
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
No description provided.