resnovas / smartcloud

A collection of epic level Github Actions. The masterminds behind our advanced Github project management.

Resnovas

smartcloud's Issues

feat(@videndum/label-mastermind): Merge sharedConfig labels option instead of replace

feature(@videndum/release-mastermind): Automatically create branches for issues

Automatically create branches for issues

feature(@videndum/release-mastermind): automatically package and release

Automatically run commands listed in the config for release and packaging

bug(util): apply label

Apply Labels removes unknown labels. This shouldn't happen

bug(release): test issue workflow

Test bug project assign workflow

feature(@videndum/release-mastermind): automatically create changelog

Automatically create changelog backed on config

feat(release): Project Card Management

My feature request explained

Tools to manage and maintain project cards

• Enforce conventions
• Synchronise card movements with remote project board (org boards)

feature(release): Assign Labels based on project card location

Assign labels based on project location

feature(@videndum/release-mastermind): HasConflict trigger

Discussed in TGTGamer/SCAA#218

^{Originally posted by ssfxate September 9, 2021}
Hey, thank you for the great GH action. I really happy with it.

Is it possible to label a PR due to occured conflict with the a branch?

Current response:

^{Originally posted by **TGTGamer** September 11, 2021} So looking through the API documentation, the simple method I was hoping would work doesn't have an endpoint that I can use. What I would need to do is compare the commits on all the pull requests and test for a conflict that way.

This information has been documented here: https://stackoverflow.com/questions/34011782/how-to-resolve-conflict-with-merging-with-github-api

I will add it to the backlog to do, however, I have other higher priority issues to address first, which will enable much-needed functionality in this action.

I will aim to have this in progress by the end of the month, once other git actions have been enabled within the action.

feat(@videndum/label-mastermind): Stale Issues

My feature request explained

Handle stale issues within label-mastermind

bug(util): Localisation issues

https://github.com/Videndum/action-masterminds/pull/187/checks?check_run_id=3187175407#step:3:28

bug(release): New error thrown when attempting to add to project "Developer Operations"

Sentry Issue: RELEASE-MASTERMIND-2C

New error thrown when attempting to add to project "Developer Operations" HttpError: Validation Failed: {"resource":"ProjectCard","code":"unprocessable","field":"data","message":"Could not resolve to a node with the global id of 'MDExOlB1bGxSZXF1ZXN0NzcxMjg0NzMy'."}: New error thrown when attempting to add to project "Developer Operations" HttpError: Validation Failed: {"resource":"ProjectCard","code":"unprocessable","field":"data","message":"Could not resolve to a node with the global id of 'MDExOlB1bGxSZXF1ZXN0...
  File "app:///../webpack:/@videndum/convential-pr-releases/lib/contexts/methods/assignProject.js", line 41, in null.<anonymous>
  File "app:///../webpack:/@videndum/convential-pr-releases/lib/contexts/methods/assignProject.js", line 38, in null.<anonymous>

feature(@videndum/release-mastermind): automatically synchronize remote repo

Synchronise remote repositories with local

feat(release): create gulp file for 24

This project now needs a gulp file to automate development operations

feature(@videndum/release-mastermind): automatically maintain branches

Automatically maintain dev and main branches for release management

bug(release): wrong type used in PRConditionConfig

https://github.com/Videndum/action-masterminds/blob/dc835239bbb677190b59b21e580388b281c53673/packages/release-mastermind/types.d.ts#L118-L121

Should be:

 export interface PRConditionConfig { 
   requires: number 
   conditions: PRCondition[] 
 } 

But throws error:

src/evaluator.ts(57,33): error TS2345: Argument of type 'PRCondition[] | Condition[] | ProjectCondition[]' is not assignable to parameter of type 'PRCondition[]'.
  Type 'ProjectCondition[]' is not assignable to type 'PRCondition[]'.
    Type 'ProjectCondition' is not assignable to type 'PRCondition'.
      Type 'ConditiononColumn' is not assignable to type 'PRCondition'.
        Property 'value' is missing in type 'ConditiononColumn' but required in type 'ConditionisApproved'.

feature(@videndum/release-mastermind)!: support new projects release (2022)

Support using the new projects via API: https://docs.github.com/en/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects

bug(util): color not updating in labels

Color doesn't work at all actually (Except documentation is generated)

config has the attribute in the following format: "color": "3ea2e6"

Originally posted by @Netail in #165 (reply in thread)

Heya @Netail, to help me identify and fix this issue, could you provide the following?

Console Logs
Please set the ACTIONS_RUNNER_DEBUG secret to true to enable debug logging, rerun the labeler workflow

Labels Config
Please could you upload a git or attach a copy of how you have your labels configured. This can either be just the label section or the entire config file depending on how large it is.

feat(release): delete labels

My feature request explained

I keep meaning to do this but keep forgetting, so lets actually create a ticket for it.

bug(util): version passing non-nodejs issue. URGENT

Bug opened in discussion: #83

Error: version returns error when should return default value

bug(release): project not found

Test project not found issue

enhance(@videndum/release-mastermind): change was isApproved handles pending approvals

Discussed in TGTGamer/SCAA#224

^{Originally posted by ssfxate September 15, 2021}
In our project we should have at least 2 approves, but requested reviewers could me more than 2.
2 isn't the max value. It's just the min value, but reviewers could be more, so approves could be more as well.

Have you got the same scheme (requirements) somewhere in a company/project?

We need to add options to mark / label as approved when there are still pending approvals.

feature(@videndum/release-mastermind): automatically achieve project cards

Automatically achieve project cards after specific period

feat(label): requests from IvanFon's repo need working on

My feature request explained

Merge all current open proposals on IvanFon

• Condition for pending reviews (IvanFon/super-labeler-action#6)
• Condition for reviews requested changes
• Condition for reviews approved
• Syntax for complex combinations of conditions (IvanFon/super-labeler-action#7)
• Able to run, test and debug action locally (IvanFon/super-labeler-action#22 && IvanFon/super-labeler-action#10)
• Check PR size and add a proper label (IvanFon/super-labeler-action#12)
• Allow adding fallback if no label match occurs (IvanFon/super-labeler-action#13)

bug(release): Validation Failed: {"resource":"ProjectCard","code":"unprocessable","field":"data"...

Sentry Issue: RELEASE-MASTERMIND-1C

HttpError: Validation Failed: {"resource":"ProjectCard","code":"unprocessable","field":"data","message":"Could not resolve to a node with the global id of 'MDU6SXNzdWUzMw=='."}
  File "app:///../webpack:/@videndum/convential-pr-releases/lib/api/project.js", line 28, in Object.create

feature(@videndum/release-mastermind): automatically approve pull requests

Automatically approve pull requests based on configuration

feat(util): Skip Label Delete

Currently, the action will default to deleting the labels which do not exist in the configuration. We need an option to change this behaviour.

bug(release): issue ID not found

Sentry Issue: RELEASE-MASTERMIND-2A

HttpError: Not Found
  File "app:///../webpack:/@videndum/convential-pr-releases/lib/utils/api/issues.js", line 16, in Utils.create

maintenance(@videndum/release-mastermind): refactor contextHandler to static call within context files

Maintenance Required

Type: Refactoring
Assignee: @TGTGamer
Risk: Low

Refactor the contextHandler.ts into ./src/contexts/ folder as static calls within classes

https://github.com/Videndum/Smartcloud/blob/5fbd201d7edfc6f32b34105a15729384bfcae134/package.json#L12-L16

Improvements

Reduction in files that need to be maintained - easier to follow code

Expected risks

Potential to break the context handling

Involved components

All components

Bug(release): external project needs to only sync on specific project

https://github.com/Videndum/action-masterminds/blob/dc835239bbb677190b59b21e580388b281c53673/packages/release-mastermind/types.d.ts#L216-L221

Should add:

   localProject: string 

To restrict the project to only sync on specific projects

docs(@videndum/release-mastermind): duplicated description that is not related to 2 of 3 points

Discussed in TGTGamer/SCAA#223

^{Originally posted by ssfxate September 13, 2021}

feat(@videndum/release-mastermind): project_card conditions

My feature request explained

Conditions and actions based on project_card context

🐛 bug(condition): Test 2

Describe the bug

To Reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behaviour

Screenshots

Console Logs

insert debug output here

Device Information

• Version: [e.g. 22]
• Platform: [e.g. macOS, Google Cloud, ubuntu 18.04]
• Browser: [e.g. stock browser, safari]
• Node Version: [e.g. v16.8.0]
• Yarn Version: [e.g. v1.22.4]
• Docker Version: [e.g. Docker version 19.03.12, build 48a66213fe]
• Package(s): [e.g. @resnovas/release-manager]
• URL: [e.g. https://console.smartcloud.gg/admin]

Additional context

Bug Checklist

• Have reproduced on my application version
• Have reproduced on a clean installation
• Have reproduced on a development build
• Have included logs or screenshots
• Have contacted support via the official website
• Have asked the community for guidance
• Have linked any related issues
• Bug confirmed by

feature(@videndum/release-mastermind): Assign to milestone

Automatically assign to milestones based on configuration

feature(@videndum/release-mastermind): automatically hotfix

Automatically replicate hotfixes to master branch