Comments (4)
Its probably me being a control freak, but I do feel its best to have a second pair of eyes at least take a cursory glance at PRs to sanity check them.
For example in #50 I just wanted to check you were happy with the added documentation, rather than you going it and re-editing it later.
from myst-parser.
I'll turn it off for now, but would like to re-instate it asap
from myst-parser.
I think it makes sense to adopt this behavior after we've moved past the initial "rapid prototyping and building stage" of myst. I think we are close to that point but there may still be some big-ish changes that will benefit from the fluidity of self-merging.
Once we think this is, say, "alpha 0.1" ready, then I agree we should either require PRs to have a review or simply adopt team practices that nobody is allowed to merge their own PR unless it is exceptional. (I have found it may be useful to make it more of a team practice than a github restriction, in the rare case that it is helpful to self merge, such as if there is a critical bug you want fixed right away)
from myst-parser.
Now is that time 😁
from myst-parser.
Related Issues (20)
- 2.0.0: documentation build fails with `'Module' object has no attribute 'doc'`
- configuration via `pyproject` HOT 3
- Add support for GitLab slugger
- Duplicate label warning from headings in module docstrings HOT 1
- Allow for links links and titles in block quote attributions HOT 9
- Anchor links to other markdown files produces " WARNING: local id not found in doc..." HOT 8
- DOC BUG: Content child 1 and Content child 2 pages look off HOT 1
- Warning "local id not found in doc" in translated docs since MyST-parser 0.19.0 HOT 4
- Add an extension to support GitHub alerts HOT 2
- Linking to documentation heading
- Numbered headings (for example starting with 1.) are not translated with Sphinx HOT 1
- `parsed-literal` does not preserve code-highlighting HOT 2
- Typo in the documentation
- Open external URLs in a new tab HOT 2
- Create a new release to capture the docutils warnings fixes HOT 2
- Cannot link to RST sections since 0.17.0 HOT 4
- 404 Page not found on "MyST - Markedly Structured Text - Parser" page HOT 1
- inline attribute on hyperlink disappears in LaTeX (but is there in HTML) HOT 1
- Line braks doesn't work. HOT 2
- third occurence of heading with the same title cannot be referenced, `[myst.xref_missing]` HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from myst-parser.