Skip to content

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

Draft
wants to merge 28 commits into
base: master
Choose a base branch
from
Draft

FAQ #27

wants to merge 28 commits into from

Conversation

davidalayachew
Copy link
Contributor

@davidalayachew davidalayachew commented Mar 17, 2025

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

  • Change must not contain extraneous whitespace

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

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.
@bridgekeeper
Copy link

bridgekeeper bot commented Mar 17, 2025

👋 Welcome back davidalayachew! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Mar 17, 2025

@davidalayachew This change is no longer ready for integration - check the PR body for details.

@openjdk
Copy link

openjdk bot commented Mar 17, 2025

⚠️ @davidalayachew a branch with the same name as the source branch for this pull request (master) is present in the target repository. If you eventually integrate this pull request then the branch master in your personal fork will diverge once you sync your personal fork with the upstream repository.

To avoid this situation, create a new branch for your changes and reset the master branch. You can do this by running the following commands in a local repository for your personal fork. Note: you do not have to name the new branch NEW-BRANCH-NAME.

$ git checkout -b NEW-BRANCH-NAME
$ git branch -f master 138e8c994a8098f26c5333a90713970d9dc42a3c
$ git push -f origin master

Then proceed to create a new pull request with NEW-BRANCH-NAME as the source branch and close this one.

@davidalayachew
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor label Mar 17, 2025
@openjdk
Copy link

openjdk bot commented Mar 17, 2025

@davidalayachew
Your change (at version d859059) is now ready to be sponsored by a Committer.

@mlbridge
Copy link

mlbridge bot commented Mar 17, 2025

Webrevs

@davidalayachew davidalayachew changed the title Adding first FAQ, per discussion in various locations lol FAQ Mar 19, 2025
… 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.
@openjdk openjdk bot removed the sponsor label Mar 19, 2025
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.
…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.
@davidalayachew davidalayachew marked this pull request as draft March 19, 2025 02:29
@davidalayachew
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant