* Add custom hover shadows
* Support avatars
* Add guide-card include
* Use it in product-landing
* Add gradient styles
* Add guides frontmatter
* Use guideArticles instead of full objects
* Add support for authors
* Add support for category header
* Just pass the whole page
* Use it
* guide.url => guide.href
* Use `*.githubusercontent.com`
* Fix mobile card width
* Remove showDescription check
* Use featureLinks.guideCards
* Forgot an if
* Remove support banner
* Just use login instead of name/avatarUrl
* Change card spacing
* Use circular avatars
* Add margin beneath "Guides"
* Use smaller font
* Even moar spacing
* Remove category
* Remove lead text, move button to bottom right
* update guide cards
* Change author of setting up ci to GitHub
* Attribute node js guide to GitHub
* Add author tag to powershell guide
* update top guides section with correct actions links
* Enforce size for single avatars
* Adjust spacing
Co-authored-by: Cynthia Rich <crichID@users.noreply.github.com>
* Don't show popular article descriptions
* Add more
* Truncate guides descriptions
* Use shorter dates, borders only on top/bottom
* Add "View all" links
* Make them go places
* Remove "View all" for Popular
* Populate some real popular articles
* Borked a thing, woopsy
* Use %B %d for full month name
* create hello world quickstart
* Fix image link
* Apply suggestions from code review
Co-authored-by: Rachael Sewell <rachmari@github.com>
* Add step to merge pull request before triggering workflow
* Add slash in front of file path
* Remove unused reusable
* more explaining in hello world quickstart
* Add invitation to create new repo
* Add experiment code
Co-authored-by: Rachael Sewell <rachmari@github.com>
Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>
* Add missing redirects
The `setting-up-and-managing-your-enterprise-account` directory was renamed to `setting-up-and-managing-your-enterprise` but most of the redirects to reflect this change were not put in place.
* Remove trailing spaces
* 💅 order
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
* Adds Travis CI migration guide
* Updated variable syntax
* Updated links
* Fixed variable
* Split into two tables to fix rendering
* Removed section about upstream, might not be applicable here
* Made formatting more consistent
* Added misc edits, "Next steps" section, matrix example
* Added small edits
* Added updates from review
* Edited "Key similarities" intro
* Replaced diagram with link to "Learning GitHub Actions"
* Moved links into a "Before you begin" section
* Added "Parallel job processing"
* Added small edits, "Default environment variables" section
* Added "Targeting specific branches"
* Added "Checking out submodules"
* Moved into nested subsection
* Updated "Assumptions about language dependencies"
* Renamed section
* Adds some small edits
* Moved all headings down 1 level
* Apply suggestions from code review
Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>
* Added updates from review
* Added updates from review
* Fixed rendering, added small edit
* Removed Travis concepts paragraph, as it seems superfluous
* Added minor edits
* Reframed the "differences" section to rather emphasize Actions features that might distinguish it from others
* Reframed additional differences to emphasize Actions capabilities
* Small edit
* More small edits
* Apply suggestions from code review
Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>
* Revised conditional example
* Revised build matrix exmple
* Updated python example
* Updated examples
* Changed example to "Building with Node.js"
* Adds fixes from peer review
* Added minor edits
* Added some finishing touches
* Update migrating-from-travis-ci-to-github-actions.md
* Small clarification
Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>
Some tweaks to the verbiage around what is provided with Premium Support and GHAE.
Instead of the "Government notification box" indicating the TSAM will inform them of the difference, I propose a secondary article, similar to how we've setup Premium Support, with something like:
For more information, see "GitHub AE Support for Commercial and Government Cloud."
This new page should house all of the roles/responsibilities for each of the two respective services in a table format that's clear and defines the support offering better.
Also, while reviewing, this seems like it should be designated with "Cloud" to denote GHES and GHE**C**:
https://docs.github.com/en/enterprise-server@2.22/admin/enterprise-support/about-github-premium-support-for-github-enterprise
to "About GitHub Premium Support for GitHub Enterprise Cloud"
So we ultimately have:
About GitHub Premium Support for GitHub Enterprise Server
About GitHub Premium Support for GitHub Enterprise Cloud
About GitHub AE Support for Commercial and Government
The navigation would simply show the Commercial/Government Cloud page under "About GitHub Enterprise Support" in the navigation so the customers can see the differences in the two and we can better explain what we provide. Both of the "About Premium Support" pages expand on a lot of good information about Premium Support.
