Skip to content
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

Add fixed schedule for Shiloh directory.yml #50

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

SHILOHSAINTS
Copy link
Contributor

No description provided.

@SHILOHSAINTS SHILOHSAINTS marked this pull request as ready for review September 12, 2024 19:34
@arjunpat
Copy link
Owner

Thanks for submitting this! Do you mind providing a little more explanation about what you are trying to do, and I can help out?

@SHILOHSAINTS
Copy link
Contributor Author

Thanks for submitting this! Do you mind providing a little more explanation about what you are trying to do, and I can help out?

So if I could have editing access or a copy of the current schs, preferably editing access, because the original creators have graduated and are no longer maintaining the daily schedule changes and many people including staff have used this and have been needing this fixed (but they don't know how) and if you don't believe me, it says the last edit was 4 years ago.
If not I can start from scratch, I have the experience to do that but maybe not the time, but that's up to you.

Thank you for this creation,
On behalf of Shiloh Christian School

@hacker-hippo
Copy link
Contributor

https://docs.github.com/en/repositories/working-with-files/managing-files/editing-files

Anybody can edit! Check this out to learn how to edit, and then follow these instructions in the readme.

@arjunpat
Copy link
Owner

@SHILOHSAINTS Thanks for taking the initiative to handle this!

The GitHub pull request system is built to handle these cases. If you edit these files (https://github.com/arjunpat/timing-data/tree/master/data/schs) and submit a pull request, I will review the updates and put them into production as soon as possible.

The format should be relatively intuitive to update. Let me know if you have any issues/questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants