Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
Plumed AlphaFold
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Deploy
Releases
Package registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Martin Kurečka
Plumed AlphaFold
Commits
c8a9bcff
There was an error fetching the commit references. Please try again later.
Commit
c8a9bcff
authored
7 years ago
by
Omar Valsson
Committed by
Giovanni
7 years ago
Browse files
Options
Downloads
Patches
Plain Diff
small fixes to dev-doc [makedoc]
parent
9768748d
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
developer-doc/usingDoxygen.md
+4
-4
4 additions, 4 deletions
developer-doc/usingDoxygen.md
with
4 additions
and
4 deletions
developer-doc/usingDoxygen.md
+
4
−
4
View file @
c8a9bcff
...
...
@@ -504,9 +504,9 @@ add [makedoc] in the commit log. After ten minutes or so the manual should be up
and to revert the commit if there are errors!
It is possible to generate PLUMED manuals for your own personal forks
(e.g. USERNAME/plumed) using the procedure
above.
using a similar procedure as described
above.
For this to work you need to enable Travis CI for your forked repository
and define th
re
e environment variables on Travis CI.
and define
appropriately
the environment variables on Travis CI.
The github account used to automatically push the generated manuals
should be defined using the GIT_BOT variable,
preferably this should be a dummy account. A github token
...
...
@@ -516,6 +516,6 @@ It is better to make all these environment variable hidden such that they are
not shown in the public logs on travis-ci.org.
To generate a manual for a specific branch you need to create a repository
USERNAME/doc-NAMEOFTHEBRANCH and give write access to the account given in
the
GIT_BOT
variable
. The generated manuals will be accessible on
GIT_BOT. The generated manuals will be accessible on
https://USERNAME.github.io/doc-NAMEOFTHEBRANCH. Note that manuals generated in
this way will always be unofficial and not shown in search engine results.
this way will always be
labeled as
unofficial and not shown in search engine results.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment