It's common when writing scripts that install or configure things to need input from the user (at a minimum, something like 'Press Enter to continue'; at a maximum, to be able to prompt the user for input, with an optional default value, and return that value).

Let's use this issue to design how that would look, and I invite suggestions!

Hi, this is a first-timers-only issue. This means we've worked to make it more legible to folks who either haven't contributed to our codebase before, or even folks who haven't contributed to open source before.

If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especia

Requirements

I think there already is an issue for each requirement, but I'll just bring it all together here.

Script files:

Your ending script file should look something like this:

// LANGUAGE: Javascript
// ENV: Node.js
// AUTHOR: Steven Copeland
// GITHUB: https://github.com/StevenCopeland

console.log("Hello World") 

Do NOT make your file like this

``

There are some repos which don't count towards hacktoberfest 2019. Try to remove those as it will save time.

Make a PR with your custom useful script. We'll merge useful scripts.

I want to work on this.

Feed : https://up-for-grabs.net/javascripts/projects.json

Currently there is an nightly process that runs on a container to create a specific json feed in Azure Container Instances.

• Do you want to add a New solution ?
• Or you solution is better than already added solution ?

Then go ahead and create a pull request. Please read Pull Request Process for simple steps to contribute

Example:

We could add more types of rate limiters, it's up to you, everything is acceptable as long as it's not already implemented by someone else.

Full-body text search

I think we need a more helpful README page. @jocelynshen started this with #25, and that's good, but I was about to comment on there that I'm not 100% sure we need links to the various subfolders in it. So, then, perhaps we should do two things to proceed forward:

1. Figure out what should go into a README (and add appropriate references to our resources page), and
2. Make those changes.