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

Figure out how to sync code in book #782

Closed
mengqiy opened this issue Jun 13, 2019 · 3 comments
Closed

Figure out how to sync code in book #782

mengqiy opened this issue Jun 13, 2019 · 3 comments
Assignees
@DirectXMan12
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone
next

Comments

@mengqiy
Copy link
Member

mengqiy commented Jun 13, 2019 •
edited

Currently we have a complete code project in the book.
It may be out-of-date when kubeubilder evolves.
We need to figure out how to sync the code and can also have a CI test to type-checking it.
One approach is:

  1. we re-generate the code and config.
  2. rebase our own document change on top of it.
    There are other approaches.

/kind feature
@mengqiy mengqiy added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 13, 2019
@droot droot removed this from Docs in 2.0.0 cross-project tracking Aug 7, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 11, 2019
@DirectXMan12
Copy link
Contributor

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 16, 2019
@camilamacedo86 camilamacedo86 added this to the next milestone Nov 3, 2020
@camilamacedo86 camilamacedo86 mentioned this issue Feb 13, 2022
Closed
3 tasks
@camilamacedo86
Copy link
Member

The proposed solution to address this need is detailed in: #2510 now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DirectXMan12 DirectXMan12

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
next
Development

No branches or pull requests
5 participants
@DirectXMan12 @mengqiy @camilamacedo86 @k8s-ci-robot @fejta-bot