-
Notifications
You must be signed in to change notification settings - Fork 28
FAQ #27
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.
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
base: master
Are you sure you want to change the base?
FAQ #27
Conversation
Let's start by creating the FAQ folder, and then the first file within it.
And now, let's link to the newly created FAQ.
👋 Welcome back davidalayachew! A progress list of the required criteria for merging this PR into |
@davidalayachew This change is no longer ready for integration - check the PR body for details. |
To avoid this situation, create a new branch for your changes and reset the
Then proceed to create a new pull request with |
/integrate |
@davidalayachew |
Webrevs
|
… jep_495_simple_source_files_and_instance_main_methods.md Names change, and people seem to know this more by the JEP #, as opposed to the name.
Need to update it here too.
Time to add the next FAQ
Little too LOUD. Of course, this will probably get ripped out, but worth doing anyways, in case the "prototype" becomes the final product lol.
Maybe adding the JEP number is unwise.
Yeah, JEP number is not wise.
…ds.md to simple_source_files_and_instance_main_methods.md If people need to know the JEP, that's easy enough to be able to find out by just looking up the feature name.
Now, we can float FAQ's between the most recent JEP Versions. Less effort for those maintaining things later.
Turned it back into draft, in anticipation of moving this work to a different branch of amber-docs. This change is getting significant enough that it makes more sense to nerge to a feature branch, then merge into main once we are happy (enough) with the results. |
Homogenizing.
I'm not married to the format. The hard work, of finding the discussions and linking them inline, is being done. Just want to make sure that we get SOMETHING out there, so that we can have a definitive place to link new folks to when they have questions, for further reading.
Progress
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/amber-docs.git pull/27/head:pull/27
$ git checkout pull/27
Update a local copy of the PR:
$ git checkout pull/27
$ git pull https://git.openjdk.org/amber-docs.git pull/27/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27
View PR using the GUI difftool:
$ git pr show -t 27
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/amber-docs/pull/27.diff
Using Webrev
Link to Webrev Comment