popcodeorg / popcodeorg/popcode
We’re not actually running Karma builds
Open
Nobody has claimed this yet.
bug
deployment
- Dominant language
- JavaScript
- Stars
- 191
- Forks
- 143
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 5
Description
I set up our test environment to run Karma builds on BrowserStack, but that is not actually happening. We can only do it when doing a build on master, because only the popcodeorg account has access to the BrowserStack credentials. But we’re not even doing it there.
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 inspecting the CI configuration for the Karma builds and the master-build path mentioned in the issue, then check how BrowserStack credentials are made available to the popcodeorg account. Done means the intended Karma build runs on master using the available BrowserStack credentials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100