Support staging site for per pull request
- Dominant language
- Java
- Stars
- 6.2k
- Forks
- 2.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 111
Description
support staging site for per pull request
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-986
- Type: Improvement
---
## Comments
07/Sep/21 21:29;githubbot;vinothchandar closed pull request #1698:
URL: https://github.com/apache/hudi/pull/1698
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@hudi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
;;;
---
07/Sep/21 21:29;githubbot;vinothchandar commented on pull request #1698:
URL: https://github.com/apache/hudi/pull/1698#issuecomment-914641622
cc @vingov wondering if we can provide something like this for the new site as well.
Closing this since we have moved off jekyll even since
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@hudi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
;;;
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start with JIRA HUDI-986 and the discussion around closed pull request #1698; the thread says the project moved off Jekyll and asks about the new site. Confirm the current site and deployment approach, then define what per-pull-request staging should support before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100