Shift from Travis CI to Github Actions

[ankushbhardwxj]

This PR aims to shift the mason registry from the existing Travis CI to Github Actions. The packages submitted by an user would be tested and built using workflows and actions. There are 2 modes of workflows : - pre-merge workflow & post-merge workflow.

• pre-merge workflow ( masonRegCI.yaml ) : This is triggered when a PR is made on the repository. This workflow is responsible for checking if a TOML file exists inside the packages in the Bricks directory. Additionally, Chapel is built and also a CI check is done in the package using mason publish --ci-check.
• post-merge workflow ( genCacheOnPush.yaml ) : This is triggered once a PR is merged and a push is made on repository. This workflow is responsible for computing a score for the package based on quality and update the cache.toml file on repository. If a package with a certain version is already present in cache, then this script is aborted and cache is not updated.

Additional post-merge changes to make :

• [ ] change credentials to that of registry
• [ ] update cache file with computed values of already present packages
• [ ] improve READMEfile to reflect new changes made and present guidelines for users.

[ankushbhardwxj]

@ben-albrecht Could you provide me the credentials for git config --global user.name and git config --global user.email for this repository ? Also, should I calculate scores for existing packages and update the cache ? (without testing them since they fail mason publish --ci-check) Another small question, would you like the checks for git tag versioning, namespace collisions, be done in our bash scripts or in mason publish --ci-check ?

[ben-albrecht]

Also, should I calculate scores for existing packages and update the cache ? (without testing them since they fail mason publish --ci-check)

Do you mean compute the scores then manually add them? This sounds reasonable to me.

Another small question, would you like the checks for git tag versioning, namespace collisions, be done in our bash scripts or in mason publish --ci-check ?

I would prefer mason publish since that gives devs an opportunity to try this locally and catch these errors before opening a PR.

[ankushbhardwxj]

@ben-albrecht Made requested changes.

• disabled on-push script genCacheOnPush.yaml by renaming it to genCacheOnPush.yaml.disabled, since only yaml files are run in Github Actions runner environment.
• refactored searchRankScript.bash to perform operations from root. Also, added verbose messages for easy debugging as follows:

  [LOG]: Package path from git command = Bricks/test/0.1.0.toml
  [LOG]: path = Bricks/test [LOG]: Package TOML file = 0.1.0.toml 
  [LOG]: Package url = https://gitlab.com/npadmana/numpylike.git 
  [LOG]: Package name = NumpyLike 
  [LOG]: Version = 0.1.0 Cloning into 'Bricks/test/newPackage'... 
  remote: Enumerating objects: 14, done. 
  remote: Counting objects: 100% (14/14), done. 
  remote: Compressing objects: 100% (10/10), done. 
  remote: Total 14 (delta 1), reused 0 (delta 0), pack-reused 0 
  Unpacking objects: 100% (14/14), done. 
  NumpyLike cloned succesfully at Bricks/test/newPackage 
  ModuleFile found in package 
  Mason.toml found in package 
  test dir found in package 
  src dir found in package 
  Found 0 examples in package. 
  Found 1 tests in package. 
  Total score generated for NumpyLike = 5 
  Wrote 'NumpyLike = 5' to cache.toml 

• Improved onpush script to use latest commit SHA in the next commit message