Skip to content

Conversation

imujjwal96
Copy link
Contributor

@imujjwal96 imujjwal96 commented Aug 24, 2017

Description

Allow users to specify branches from their registered repositories settings at Yaydoc. User may also delete some of the specified branches.
If no branches are specified, documentation will be generated from all branches containing .yaydoc.yml file, except the gh-pages branch

Related Issue

Fixes #358

Motivation and Context

The documentation for a registered repository is generated at every commit made to the repository. This process happens in commits made to any of the repository's branches except for branches that do not have a .yaydoc.yml file and the gh-pages branch. It would be nice if the user can limit the doc generation process to a specific branch or a couple of branches

How Has This Been Tested?

Test at https://yaydoc7.herokuapp.com

Types of changes

  • Bug fix
  • New feature

Checklist:

  • I have read the Contribution & Best practices Guide and my PR follows them.
  • There is a corresponding issue for this pull request.
  • Mentioned the Issue number in the pull request commit message Fixes #<number> commit message
  • There is only one commit per issue.

@imujjwal96
Copy link
Contributor Author

@pri22296 @Sch00lb0y Please review.

@@ -1,10 +1,9 @@
$(function() {
const predefinedMessages = {
'mail_disabled_successful': "Mail service disabled for this repository",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these messages no longer needed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No we are not showing them now. We have added a toggle for these events and we show a check mark beside the element when the change is successful

@pri22296
Copy link
Member

@imujjwal96 Shows null after adding and deleting branches

screenshot 218

@imujjwal96
Copy link
Contributor Author

@pri22296 I am not able to reproduce this error

@pri22296
Copy link
Member

@imujjwal96 Let me test this more and i'll get back to you If I can reproduce it.

@pri22296
Copy link
Member

@imujjwal96 I'm not able to reproduce that error. It wold be great though if you could take a look at the code and just ensure that everything is fine.

Also submit button gets hidden when there are >=3 branches.
screenshot 219

@imujjwal96
Copy link
Contributor Author

Also submit button gets hidden when there are >=3 branches.
does it create any problem? I thought users may not submit the form without closing the select tag

@pri22296
Copy link
Member

The UI feels awkward there. consider showing the branches with a scroll bar and having the submit button slightly below.

@imujjwal96
Copy link
Contributor Author

@pri22296 Updated it.

pri22296
pri22296 previously approved these changes Aug 26, 2017
@ghost ghost removed the needs-review label Aug 26, 2017
}, function (error, response, body) {
if (error) {
callback(error);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pass null in the second parameter. it look consistent

@imujjwal96
Copy link
Contributor Author

@pri22296 @Sch00lb0y Updated

@mariobehling mariobehling merged commit f2b0817 into fossasia:master Aug 27, 2017
@ghost ghost added the ready-to-ship label Aug 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants