#5019 closed task (blessed) (fixed)
Switch to `manifest.json` in Block Editor docs importer
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Component: | Developer Hub | Keywords: | commit |
| Cc: |
Description
In #4388 we set up a manifest-devhub.json file in the block editor repo as the source for the devhub manifest.
The patch (to be attached) reverts it to use manifest.json. I've also rebased the associated PR in the Gutenberg repo, so it's ready to go.
Attachments (1)
Change History (10)
This ticket was mentioned in Slack in #meta-devhub by chrisvanpatten. View the logs.
5 years ago
This ticket was mentioned in Slack in #core-editor by chrisvanpatten. View the logs.
5 years ago
#3
@
5 years ago
Note: the Gutenberg PR should be merged first, because the current manifest.json file is fairly out of date. If this patch is merged first, it could cause some out-of-date pages to appear.
#4
@
5 years ago
- Keywords commit added
Looks good to me, I've approved the GB PR, so once this lands, the GB PR can be merged
Edit: I merged the GB PR so this is ready for commit
#5
@
5 years ago
- Component changed from Handbooks to Developer Hub
Oops, this was in the wrong component. My bad!
This ticket was mentioned in Slack in #docs by chrisvanpatten. View the logs.
5 years ago
#7
@
5 years ago
- Owner set to coffee2code
- Resolution set to fixed
- Status changed from new to closed
In 9482:
#8
@
5 years ago
@chrisvanpatten: I believe there has been some talk in places that the manifest should point to a copy in a branch tied to the latest WP release. Should that be the next step, so that the handbook on DevHub doesn't reflect features and changes present in the master branch but not packaged with the latest WP?
Patch to revert to manifest.json