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

Procedural scheduling documentation #184

Merged
merged 7 commits into from
Sep 10, 2024
Merged

Conversation

JoelCourtney
Copy link
Contributor

@JoelCourtney JoelCourtney commented Sep 3, 2024

In addition to creating the procedural scheduling and timeline docs, this also reorganizes all of the constraints/scheduling docs to put all of it under one heading. This is because constraints and scheduling, eDSL and procedural, are all very related and coupled and I don't think it makes sense to teach them separately.

@JoelCourtney JoelCourtney force-pushed the feat/procedural-scheduling branch 4 times, most recently from ab2a078 to 443c135 Compare September 5, 2024 00:53
@JoelCourtney JoelCourtney changed the title WIP procedural scheduling docs Procedural scheduling documentation Sep 5, 2024
@JoelCourtney JoelCourtney force-pushed the feat/procedural-scheduling branch 2 times, most recently from 1208d39 to 9e9f7c2 Compare September 6, 2024 00:33
@JoelCourtney JoelCourtney force-pushed the feat/procedural-scheduling branch from 9e9f7c2 to a545229 Compare September 6, 2024 01:28
Copy link
Collaborator

@dandelany dandelany left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Approved - will come back to these in v2 for more improvements. Thanks!

@dandelany dandelany merged commit 09819b5 into develop Sep 10, 2024
1 check passed
@dandelany dandelany deleted the feat/procedural-scheduling branch September 10, 2024 00:26
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.

2 participants