{"meta":{"title":"Creating new files","intro":"You can create new files directly on GitHub in any repository you have write access to.","product":"Repositories","breadcrumbs":[{"href":"/en/repositories","title":"Repositories"},{"href":"/en/repositories/working-with-files","title":"Work with files"},{"href":"/en/repositories/working-with-files/managing-files","title":"Managing files"},{"href":"/en/repositories/working-with-files/managing-files/creating-new-files","title":"Creating new files"}],"documentType":"article"},"body":"# Creating new files\n\nYou can create new files directly on GitHub in any repository you have write access to.\n\nWhen creating a file on GitHub, consider the following:\n\n* If you try to create a new file in a repository that you don’t have access to, we will fork the project to your personal account and help you send [a pull request](/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) to the original repository after you commit your change.\n* File names created via the web interface can only contain alphanumeric characters and hyphens (`-`). To use other characters, [create and commit the files locally, then push them to the repository on GitHub](/en/repositories/working-with-files/managing-files/adding-a-file-to-a-repository).\n* Your repository may have push rulesets enabled. Push rulesets may block creating a new file in the repository based on certain restrictions. Push rulesets apply to the repository's entire fork network. Which means that any push rulesets that are configured in the root repository will also apply to every fork of the repository. For more information, see [About rulesets](/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets#about-rulesets).\n\n> \\[!WARNING]\n> Never `git add`, `commit`, or `push` sensitive information, for example passwords or API keys, to a remote repository. If you've already added this information, see [Removing sensitive data from a repository](/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository).\n\n1. On GitHub, navigate to the main page of the repository.\n\n2. In your repository, browse to the folder where you want to create a file.\n\n3. Above the list of files, select the **Add file** dropdown menu, then click ** Create new file**.\n\n Alternatively, you can click in the file tree view on the left.\n\n \n\n4. In the file name field, type the name and extension for the file. To create subdirectories, type the `/` directory separator.\n\n5. In the file contents text box, type content for the file.\n\n6. To review the new content, above the file contents, click **Preview**.\n \n\n7. Click **Commit changes...**\n\n8. In the \"Commit message\" field, type a short, meaningful commit message that describes the change you made to the file. You can attribute the commit to more than one author in the commit message. For more information, see [Creating a commit with multiple authors](/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors).\n\n9. If you have more than one email address associated with your account on GitHub, click the email address drop-down menu and select the email address to use as the Git author email address. Only verified email addresses appear in this drop-down menu. If you enabled email address privacy, then a no-reply will be the default commit author email address. For more information about the exact form the no-reply email address can take, see [Setting your commit email address](/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address).\n\n \n\n10. Below the commit message fields, decide whether to add your commit to the current branch or to a new branch. If your current branch is the default branch, you should choose to create a new branch for your commit and then create a pull request. For more information, see [Creating a pull request](/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request).\n\n \n\n11. Click **Commit changes** or **Propose changes**."}