Thank you for your interest in our documentation! The best ways to help make this documentation better for everyone are to:
Most of this repo's content is generated from type definition files. As such, corrections here are likely to be overwritten. Please report issues or make requests for additional documentation through GitHub Issues. To do this, go to the Feedback section at the bottom of the affected article, then select This page to create a GitHub issue. Alternatively, create a new issue directly on GitHub.
Important: The reference content in this repository is autogenerated. Please read the documentation tooling notes if you're planning to edit files not mentioned in this section.
Code samples found in documentation from this repo come from two places:
- /docs/code-snippets
- OfficeDev/office-js-snippets (The source of Script Lab samples)
Contributions to the Script Lab sample repo are covered in that repo's readme.
The /docs/code-snippets/*-snippets.yaml files in this repo contain samples for each application and the Common APIs. Each YAML key in one of those YAML files is the UID of a field in the documentation. The keys follow the format <Application>.<ClassName>#<fieldName>:member<overloadNumber(methods only)>. Add your sample code snippet as the value under the key of the field you're using in a sample. Use the following Git mechanisms to submit changes to the repo.
- To make small changes to a sample, Contribute using GitHub.
- To make large changes, Contribute using Git.
We'll review each PR to make sure it meets Microsoft standards. To help ensure your sample gets integrated into the reference documentation, keep the following tips in mind.
- Limit the scope. Sample code that focuses on a small scenario or API usage helps readers understand how that API is used. (Larger samples should go to Script Lab or the Code samples repo.)
- Include a brief comment explaining the intended behavior.
- Clearly state the expected input or state.
Use GitHub to contribute to this documentation without having to clone the repo to your desktop. This is the easiest way to create a pull request in this repository. Use this method to make a minor change that doesn't involve code changes.
Using this method allows you to contribute to one article at a time.
- Find the article you want to contribute to on GitHub.
- Once you are on the article in GitHub, sign in to GitHub (to get a free account, Join GitHub).
- Choose the pencil icon (edit the file in your fork of this project) and make your changes in the <>Edit file window.
- Scroll to the bottom and enter a description.
- Choose Propose file change > Create pull request.
You now have successfully submitted a pull request. Pull requests are typically reviewed within 10 business days. Your changes will not necessarily be published immediately after your pull request is accepted. There is a further publication step that is done internally by Microsoft that typically will happen within a few days.
Use Git to contribute substantive changes, such as:
- Contributing code.
- Contributing changes that affect meaning.
- Contributing large changes to text.
- Adding new topics.
-
If you don't have a GitHub account, set one up at GitHub.
-
After you have an account, install Git on your computer. Follow the steps in the Set up Git tutorial.
-
To submit a pull request using Git, follow the steps in Use GitHub, Git, and this repository.
-
You will be asked to sign the Contributor's License Agreement if you are:
- A member of the Microsoft Open Technologies group.
- A contributor who doesn't work for Microsoft.
As a community member, you must sign the Contribution License Agreement (CLA) before you can contribute large submissions to a project. You only need to complete and submit the documentation once. Carefully review the document. You may be required to have your employer sign the document.
Signing the CLA does not grant you rights to commit to the main repository, but it does mean that the Office Developer and Office Developer Content Publishing teams will be able to review and approve your contributions. You are credited for your submissions.
Note: Most of the information in this section can be found in GitHub Help articles. If you're familiar with Git and GitHub, skip to the Contribute and edit content section for the specifics of the code/content flow of this repository.
-
Set up a GitHub account so you can contribute to this project. If you haven't done this, go to GitHub and do it now.
-
Install Git on your computer. Follow the steps in the Set up Git tutorial.
-
Create your own fork of this repository. To do this, at the top of the page, choose the Fork button.
-
Copy your fork to your computer. To do this, open Git Bash. At the command prompt enter:
git clone https://github.com/<your user name>/office-js-docs-reference.gitNext, create a reference to the root repository by entering these commands:
cd office-js-docs-reference git remote add upstream https://github.com/OfficeDev/office-js-docs-reference.git git fetch upstream
Congratulations! You've now set up your repository. You won't need to repeat these steps again.
To make the contribution process as seamless as possible, follow these steps.
- Create a new branch.
- Add new content or edit existing content.
- Submit a pull request to the main repository.
- Delete the branch.
Important: Limit each branch to a single concept/article to streamline the work flow and reduce the chance of merge conflicts. Content appropriate for a new branch includes:
- A new article.
- Spelling and grammar edits.
- Applying a single formatting change across a large set of articles (for example, applying a new copyright footer).
- Open Git Bash.
- At the Git Bash command prompt, type
git pull upstream main:<new branch name>. This creates a new branch locally that is copied from the latest OfficeDev main branch. - At the Git Bash command prompt, type
git push origin <new branch name>. This alerts GitHub to the new branch. You should now see the new branch in your fork of the repository on GitHub. - At the Git Bash command prompt, type
git checkout <new branch name>to switch to your new branch.
You navigate to the repository on your computer by using File Explorer. The repository files are in C:\Users\<your username>\office-js-docs-reference.
To edit files, open them in an editor of your choice and modify them. To create a new file, use the editor of your choice and save the new file in the appropriate location in your local copy of the repository. While working, save your work frequently.
The files in C:\Users\<your username>\office-js-docs-reference are a working copy of the new branch that you created in your local repository. Changing anything in this folder doesn't affect the local repository until you commit a change. To commit a change to the local repository, type the following commands in Git Bash.
git add .
git commit -v -a -m "<Describe the changes made in this commit>"
The add command adds your changes to a staging area in preparation for committing them to the repository. The period after the add command specifies that you want to stage all of the files that you added or modified, checking subfolders recursively. (If you don't want to commit all of the changes, you can add specific files. You can also undo a commit. For help, type git add -help or git status.)
The commit command applies the staged changes to the repository. The switch -m means you are providing the commit comment in the command line. The -v and -a switches can be omitted. The -v switch is for verbose output from the command, and -a does what you already did with the add command.
You can commit multiple times while you are doing your work, or you can commit once when you're done.
When you're finished with your work and are ready to have it merged into the main repository, follow these steps.
- In the Git Bash command prompt, type
git push origin <new branch name>. In your local repository,originrefers to your GitHub repository that you cloned the local repository from. This command pushes the current state of your new branch, including all commits made in the previous steps, to your GitHub fork. - On the GitHub site, navigate in your fork to the new branch.
- Choose the Pull Request button at the top of the page.
- Verify the Base branch is
OfficeDev/office-js-docs-reference@mainand the Head branch is<your username>/office-js-docs-reference@<branch name>. - Choose the Update Commit Range button.
- Add a title to your pull request, and describe all the changes you're making.
- Submit the pull request.
One of the site administrators will process your pull request. Your pull request will surface on the OfficeDev/office-js-docs-reference site under Pull requests. When the pull request is accepted, the issue will be resolved. Your changes will not necessarily be published immediately after your pull request is accepted. There is a further publication step that is done internally by Microsoft that typically will happen within a few days.
After a branch is successfully merged (that is, your pull request is accepted), don't continue working in that local branch. This can lead to merge conflicts if you submit another pull request. To do another update, create a new local branch from the successfully merged upstream branch, and then delete your initial local branch.
For example, if your local branch X was successfully merged into the OfficeDev/office-js-docs-reference main branch and you want to make additional updates to the content that was merged. Create a new local branch, X2, from the OfficeDev/office-js-docs-reference main branch. To do this, open Git Bash and execute the following commands.
cd office-js-docs-reference
git pull upstream main:X2
git push origin X2
You now have local copies (in a new local branch) of the work that you submitted in branch X. The X2 branch also contains all the work other writers have merged, so if your work depends on others' work (for example, shared images), it is available in the new branch. You can verify that your previous work (and others' work) is in the branch by checking out the new branch...
git checkout X2
...and verifying the content. (The checkout command updates the files in C:\Users\<your username>\office-js-docs-reference to the current state of the X2 branch.) Once you check out the new branch, you can make updates to the content and commit them as usual. However, to avoid working in the merged branch (X) by mistake, it's best to delete it (see the following Delete a branch section).
Once your changes are successfully merged into the main repository, delete the branch you used because you no longer need it. Any additional work should be done in a new branch.
- In the Git Bash command prompt, type
git checkout main. This ensures that you aren't in the branch to be deleted (which isn't allowed). - Next, at the command prompt, type
git branch -d <branch name>. This deletes the branch on your computer only if it has been successfully merged to the upstream repository. (You can override this behavior with the–Dflag, but first be sure you want to do this.) - Finally, type
git push origin :<branch name>at the command prompt (a space before the colon and no space after it). This will delete the branch on your GitHub fork.
Congratulations, you have successfully contributed to the project!
Fill out the form at Join GitHub to open a free GitHub account.
You will automatically be sent a notice that you need to sign the Contributor's License Agreement (CLA) if your pull request requires one.
As a community member, you must sign the Contribution License Agreement (CLA) before you can contribute large submissions to this project. You only need to complete and submit the documentation once. Carefully review the document. You may be required to have your employer sign the document.
When you submit your changes, via a pull request, our team will be notified and will review your pull request. You will receive notifications about your pull request from GitHub; you may also be notified by someone from our team if we need more information. If your pull request is approved, we'll update the documentation. We reserve the right to edit your submission for legal, style, clarity, or other issues.
Currently, we are not allowing external contributors to approve pull requests in this repository.
Pull requests are typically reviewed within 10 business days.
- To learn more about using Git and GitHub, first check out the GitHub Help.