This repository has been archived by the owner on Sep 29, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 94
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #147 from AzureAD/release-0.6.0
Release 0.6.0
- Loading branch information
Showing
21 changed files
with
508 additions
and
22 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -27,7 +27,7 @@ | |
|
||
# pylint: disable=wrong-import-position | ||
|
||
__version__ = '0.5.1' | ||
__version__ = '0.6.0' | ||
|
||
import logging | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,126 @@ | ||
# CONTRIBUTING | ||
|
||
Azure Active Directory SDK projects welcomes new contributors. This document will guide you | ||
through the process. | ||
|
||
### CONTRIBUTOR LICENSE AGREEMENT | ||
|
||
Please visit [https://cla.microsoft.com/](https://cla.microsoft.com/) and sign the Contributor License | ||
Agreement. You only need to do that once. We can not look at your code until you've submitted this request. | ||
|
||
|
||
### FORK | ||
|
||
Fork the project [on GitHub][] and check out | ||
your copy. | ||
|
||
Example for ADAL Python: | ||
|
||
``` | ||
$ git clone [email protected]:username/azure-activedirectory-library-for-python.git | ||
$ cd azure-activedirectory-library-for-python | ||
$ git remote add upstream [email protected]:AzureAD/azure-activedirectory-library-for-python.git | ||
``` | ||
|
||
Now decide if you want your feature or bug fix to go into the dev branch | ||
or the master branch. **All bug fixes and new features should go into the dev branch.** | ||
|
||
The master branch is effectively frozen; patches that change the SDKs | ||
protocols or API surface area or affect the run-time behavior of the SDK will be rejected. | ||
|
||
Some of our SDKs have bundled dependencies that are not part of the project proper. Any changes to files in those directories or its subdirectories should be sent to their respective | ||
projects. Do not send your patch to us, we cannot accept it. | ||
|
||
In case of doubt, open an issue in the [issue tracker][]. | ||
|
||
Especially do so if you plan to work on a major change in functionality. Nothing is more | ||
frustrating than seeing your hard work go to waste because your vision | ||
does not align with our goals for the SDK. | ||
|
||
|
||
### BRANCH | ||
|
||
Okay, so you have decided on the proper branch. Create a feature branch | ||
and start hacking: | ||
|
||
``` | ||
$ git checkout -b my-feature-branch | ||
``` | ||
|
||
### COMMIT | ||
|
||
Make sure git knows your name and email address: | ||
|
||
``` | ||
$ git config --global user.name "J. Random User" | ||
$ git config --global user.email "[email protected]" | ||
``` | ||
|
||
Writing good commit logs is important. A commit log should describe what | ||
changed and why. Follow these guidelines when writing one: | ||
|
||
1. The first line should be 50 characters or less and contain a short | ||
description of the change prefixed with the name of the changed | ||
subsystem (e.g. "net: add localAddress and localPort to Socket"). | ||
2. Keep the second line blank. | ||
3. Wrap all other lines at 72 columns. | ||
|
||
A good commit log looks like this: | ||
|
||
``` | ||
fix: explaining the commit in one line | ||
Body of commit message is a few lines of text, explaining things | ||
in more detail, possibly giving some background about the issue | ||
being fixed, etc etc. | ||
The body of the commit message can be several paragraphs, and | ||
please do proper word-wrap and keep columns shorter than about | ||
72 characters or so. That way `git log` will show things | ||
nicely even when it is indented. | ||
``` | ||
|
||
The header line should be meaningful; it is what other people see when they | ||
run `git shortlog` or `git log --oneline`. | ||
|
||
Check the output of `git log --oneline files_that_you_changed` to find out | ||
what directories your changes touch. | ||
|
||
|
||
### REBASE | ||
|
||
Use `git rebase` (not `git merge`) to sync your work from time to time. | ||
|
||
``` | ||
$ git fetch upstream | ||
$ git rebase upstream/v0.1 # or upstream/master | ||
``` | ||
|
||
|
||
### TEST | ||
|
||
Bug fixes and features should come with tests. Add your tests in the | ||
test directory. This varies by repository but often follows the same convention of /src/test. Look at other tests to see how they should be | ||
structured (license boilerplate, common includes, etc.). | ||
|
||
|
||
Make sure that all tests pass. | ||
|
||
|
||
### PUSH | ||
|
||
``` | ||
$ git push origin my-feature-branch | ||
``` | ||
|
||
Go to https://github.com/username/azure-activedirectory-library-for-***.git and select your feature branch. Click | ||
the 'Pull Request' button and fill out the form. | ||
|
||
Pull requests are usually reviewed within a few days. If there are comments | ||
to address, apply your changes in a separate commit and push that to your | ||
feature branch. Post a comment in the pull request afterwards; GitHub does | ||
not send out notifications when you add commits. | ||
|
||
|
||
[on GitHub]: https://github.com/AzureAD/azure-activedirectory-library-for-python | ||
[issue tracker]: https://github.com/AzureAD/azure-activedirectory-library-for-python/issues |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
# Minimal makefile for Sphinx documentation | ||
# | ||
|
||
# You can set these variables from the command line. | ||
SPHINXOPTS = | ||
SPHINXBUILD = sphinx-build | ||
SPHINXPROJ = ADALPython | ||
SOURCEDIR = source | ||
BUILDDIR = build | ||
|
||
# Put it first so that "make" without argument is like "make help". | ||
help: | ||
@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O) | ||
|
||
.PHONY: help Makefile | ||
|
||
# Catch-all target: route all unknown targets to Sphinx using the new | ||
# "make mode" option. $(O) is meant as a shortcut for $(SPHINXOPTS). | ||
%: Makefile | ||
@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
@ECHO OFF | ||
|
||
pushd %~dp0 | ||
|
||
REM Command file for Sphinx documentation | ||
|
||
if "%SPHINXBUILD%" == "" ( | ||
set SPHINXBUILD=sphinx-build | ||
) | ||
set SOURCEDIR=source | ||
set BUILDDIR=build | ||
set SPHINXPROJ=ADALPython | ||
|
||
if "%1" == "" goto help | ||
|
||
%SPHINXBUILD% >NUL 2>NUL | ||
if errorlevel 9009 ( | ||
echo. | ||
echo.The 'sphinx-build' command was not found. Make sure you have Sphinx | ||
echo.installed, then set the SPHINXBUILD environment variable to point | ||
echo.to the full path of the 'sphinx-build' executable. Alternatively you | ||
echo.may add the Sphinx directory to PATH. | ||
echo. | ||
echo.If you don't have Sphinx installed, grab it from | ||
echo.http://sphinx-doc.org/ | ||
exit /b 1 | ||
) | ||
|
||
%SPHINXBUILD% -M %1 %SOURCEDIR% %BUILDDIR% %SPHINXOPTS% | ||
goto end | ||
|
||
:help | ||
%SPHINXBUILD% -M help %SOURCEDIR% %BUILDDIR% %SPHINXOPTS% | ||
|
||
:end | ||
popd |
Empty file.
Oops, something went wrong.