Skip to content

Conversation

@developer982
Copy link

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation (add or update README or docs)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

kotewar and others added 30 commits May 30, 2022 06:36
…ons-cache-version

Upgraded @actions/cache to 2.0.5
Add sample cache for Erlang with Rebar3
…ache-to-v2.0.6

Updated @actions/cache to v2.0.6
…ache-to-v2.0.6

Updated README file with release info
Fixed bad yaml in README example
The default `STACK_ROOT` is `~/.stack` only on Unix-like operating systems. On Windows, the default is `%APPDATA%/stack` (usually `%HOME%\AppData\Roaming\stack`).

On Unix-like OSs, Stack stores GHC and other tools in a `programs` directory in the `STACK_ROOT`. On Windows, Stack stores those tools and MSYS2 in `%LOCALAPPDATA%\Programs\stack` (usually `%HOME%\AppData\Local\Programs\stack`).
Fixes autoassign reviewer for PRs from forked repos.
Adapt existing Haskell Stack example for Windows
In Clojure, Lein tool is used to generate template for various projects.
Lein project metadata (including project dependencies) are stored in
prject.clj (in root directory) file. Lein downloads dependencies in
classpath (~/.m2/repository). So here I am caching ~/.m2/repository path
for reusing cache in subsequent builds.
Add kotewar and remove phantsure from auto-assignees lists
Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>
Make it more obvious that the cache call does double duty
* Consuming 3.0 actions/cache

* formatting and error

* updated package version

* resolve package

* dist

* review comment

* dist

* dist
@developer982 developer982 requested a review from a team as a code owner May 26, 2024 06:11
@joshmgross joshmgross added the invalid This doesn't seem right label Jun 6, 2024
@joshmgross joshmgross closed this Jun 6, 2024
@Ottapettavan
Copy link

Ottapettavan commented Jun 19, 2024

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation (add or update README or docs)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

invalid This doesn't seem right

Projects

None yet

Development

Successfully merging this pull request may close these issues.