petercort opened a new pull request, #8088:
URL: https://github.com/apache/incubator-devlake/pull/8088
… org repos, and pulls the repository data when adding scope
previous behavior would return a single repository. Also no repo data was
returned so the user could not add the repo to devlake
fixes part of my issue in #7655
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
### ⚠️ Pre Checklist
> Please complete _ALL_ items in this checklist, and remove before submitting
- [ ] I have read through the [Contributing
Documentation](https://devlake.apache.org/community/).
- [ ] I have added relevant tests.
- [ ] I have added relevant documentation.
- [ ] I will add labels to the PR, such as `pr-type/bug-fix`,
`pr-type/feature-development`, etc.
<!--
Thanks for submitting a pull request!
We appreciate you spending the time to work on these changes.
Please fill out as many sections below as possible.
-->
### Summary
Removees the processed org check which was preventing multiple repositories
from being pulled. The processed org check would trigger after a single repo
was returned. Also I've added in the repo data model because it wasn't
returning data, and therefore data couldn't be added to the scope!
### Does this close any open issues?
Partial fix for #7655
### Screenshots
Include any relevant screenshots here.
### Other Information
I'm not sure what the initial purpose the processedOrgs check had, so
deleting it entirely might be aggressive. But since the app connection is
scoped to a single org I don't see a direct downside to removing it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
