Searched full:pages (Results 1 – 6 of 6) sorted by relevance
1 # Simple workflow for deploying static content to GitHub Pages2 name: Deploy static content to GitHub Pages7 branches: [gh-pages]12 # Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages15 pages: write21 group: "pages"28 name: github-pages35 - name: Setup Pages36 uses: actions/configure-pages@v539 uses: actions/upload-pages-artifact@v3[all …]
35 gh-pages-branch: gh-pages
272 .pages b {280 .pages {
6 <tab type="pages" visible="yes" title="Usage and Description" intro=""/>
369 //if (rootBase=="index" || rootBase=="pages" || rootBase=="search")
57 # title of most generated pages and in a few other places.451 # instead of on a separate page (for HTML and Man pages) or section (for LaTeX465 # Man pages) or section (for LaTeX and RTF).810 # layout of pages" for information.1710 # If you want full control over the layout of the generated HTML pages it might2213 # If the GENERATE_MAN tag is set to YES, doxygen will generate man pages for2219 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a2229 # man pages. In case the manual section does not start with a number, the number2238 # MAN_OUTPUT in which the man pages are placed. If defaults to man followed by2263 # The XML_OUTPUT tag is used to specify where the XML pages will be put. If a[all …]
