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.

Sign up for GitHub

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

Jump to bottom

[Documentation] automatically update documentation after PR is merged. #206

Closed
azjezz opened this issue Jun 3, 2021 · 1 comment
Closed

[Documentation] automatically update documentation after PR is merged. #206

azjezz opened this issue Jun 3, 2021 · 1 comment
Assignees
@azjezz
Labels
Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Accepted It's clear what the subject of the issue is about, and what the resolution should be. Type: Enhancement Most issues will probably ask for additions or changes.
Milestone
2.0.0

Comments

@azjezz
Copy link
Owner

azjezz commented Jun 3, 2021

Having contributors run php doc/documentor.php after every little change is annoying ( see #205 ), we should automate this via GitHub actions.
@azjezz azjezz added the Type: Enhancement Most issues will probably ask for additions or changes. label Jun 3, 2021
@azjezz azjezz added this to the 1.8.0 milestone Jun 3, 2021
@azjezz azjezz self-assigned this Jun 3, 2021
@azjezz azjezz added Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Accepted It's clear what the subject of the issue is about, and what the resolution should be. labels Jun 3, 2021
@azjezz azjezz modified the milestones: 1.8.0, 1.9.0 Sep 8, 2021
@veewee veewee mentioned this issue Oct 7, 2021
Merged
@azjezz azjezz modified the milestones: 1.9.0, 2.0.0 Oct 29, 2021
@azjezz
Copy link
Owner Author

azjezz commented Nov 8, 2021

closed in favor of #260

@azjezz azjezz closed this as completed Nov 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@azjezz azjezz

Labels
Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Accepted It's clear what the subject of the issue is about, and what the resolution should be. Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Milestone
2.0.0
Development

No branches or pull requests
1 participant
@azjezz