mitre / mitre/saf-lambda-function
Merge branches
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 4
- Avg merge
- 1m
- Merged PRs (30d)
- 5
Description
Some approaches to consider while merging branches:
- Create separate folders for common and major use cases. (Reference)
- Combine the serverless.yaml and add conditions using the IfElse plugin depending on user's selections
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current branch layout and serverless.yaml, then compare the separate-folder approach in the linked serverless/examples reference with the IfElse plugin approach. The issue is complete only after one merging strategy is chosen and the branches are consolidated consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- backend, cloud
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100