Skip to content
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

Contribute to upstream #435

Merged

Conversation

MichaelTsengLZ
Copy link
Contributor

@MichaelTsengLZ MichaelTsengLZ commented Apr 24, 2019

Bugfixes:

  1. Whitelist should use exact match when there is no wildcard (*). We don't want to pass a foo-like-user when we white list foo.
  2. When updating a linked repo, we should validate input. And should allow whiteListPattern and privacyPolicy as empty string.
  3. Fix small issues when updating org/repo in UI.
  4. Do not get pull request files to check significant changes, there is enough information in the pull request itself. In this way, we could avoid the Github abuse exception when there are thousands of commits in a pull request.

Security:

  1. Setup cookie secure

New feature:

  1. Add readiness route so that Kubernetes could better swap pods.
  2. Show CLA updated date in the CLA signing page.

Refactor:
The refactor is mainly about placing callbacks with promises. It helps to clean the code and easily add key metrics.

@coveralls
Copy link

coveralls commented Apr 24, 2019

Coverage Status

Coverage increased (+0.3%) to 90.351% when pulling e67e2d2 on microsoft:miczeng/contributeToUpStream into c6a02bc on cla-assistant:master.

@MichaelTsengLZ MichaelTsengLZ force-pushed the miczeng/contributeToUpStream branch 3 times, most recently from f722a78 to 060a03f Compare April 25, 2019 19:48
* Add CLA updated date as version.

* Nitfix: CLA signing page headline should show shared gist information.
When pull request is really big, like thousands of commits, getPullRequestFiles will try to get all commits.
These will abuse github api. Use getPR() api instead.
1. Should be able to link null gist cla
2. Update linked item should not delete the gist info
1. Should allow the value of whiteListPattern and privacyPolicy to be empty string when they were cleaned up in UI.
2. Should validate repo input when updating linked repo.
3. Add test for api/repo
For example, we don't want user named 'Intel-like' pass our CCLA when 'Intel' is in the whitelist.
src/server/api/org.js Outdated Show resolved Hide resolved
src/server/documents/utils.js Show resolved Hide resolved
@KharitonOff KharitonOff merged commit 1711c2a into cla-assistant:master May 21, 2019
@KharitonOff
Copy link
Contributor

Thank you!

KharitonOff added a commit that referenced this pull request Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants